You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Sometimes when a computer starts up, writing to the projector's FB will cause a segfault, sometimes restarting the VM fixes it inconsistently, and sometimes its broken every time, and only restarting the gameserver fixes it, its super inconsistent, but generally can be triggered quite quickly by just restarting a computer with a framebuffer a bunch, then trying to write to it using some app like fbv, where it immediately segfaults
To Reproduce
Steps to reproduce the behavior:
Multiplayer 1.18.2, forge latest
Make a computer, put linux on it, connect a projector
Boot computer, try to use an app like fbv (my custom rewrite is available here fbz.zipsource code, but any version of fbv or similar will trigger the problem)
Sometimes the app will segfault upon trying to write any of the data, sometimes it wont, and restarting the VM will only sometimes fix it
Log files
nothing oc2 related in either log file, but here is server log
Expected behavior
Framebuffer works like, and you can write data to it at will
Screenshots
N/A, its just an app segfaulting
Versions (please complete the following information):
Narrowed it down more, the segfault only occurrs when you mmap then write to the framebuffer, if you use standard filesystem syscalls access to write to the framebuffer, it always seems to work
Describe the bug
Sometimes when a computer starts up, writing to the projector's FB will cause a segfault, sometimes restarting the VM fixes it inconsistently, and sometimes its broken every time, and only restarting the gameserver fixes it, its super inconsistent, but generally can be triggered quite quickly by just restarting a computer with a framebuffer a bunch, then trying to write to it using some app like fbv, where it immediately segfaults
To Reproduce
Steps to reproduce the behavior:
Log files
nothing oc2 related in either log file, but here is server log
Expected behavior
Framebuffer works like, and you can write data to it at will
Screenshots
N/A, its just an app segfaulting
Versions (please complete the following information):
Additional context
While this is a modified version of oc2, none of the patches applied effect the particular code at play
The text was updated successfully, but these errors were encountered: