-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash after running mpv
#8325
Comments
Reproduced with default settings.
Downloaded lots of random videos and started opening all of them with
|
Since the segmentation violation occurs inside |
This looks like a memory corruption issue. These things are notoriously hard to track down but there are steps you can take to make it easier. Please try running sway using an address sanitizer. This will validate that all memory accesses sway attempts are valid and so it doesn't corrupt itself along with any chance of debugging it. |
@Nefsen402 OK. I've just finished building |
I was not able to reproduce the problem while running a
Spent quite a bit of time trying to trigger it but no crash. |
The crash maybe fixed on sway master and exclusive to version 1.9. I would recommend you keep running a snapshot of git that you are happy with until a real release happens. |
Please fill out the following:
Sway Version:
Configuration File:
Stack Trace:
bt full
source
variable appears to be corruptinterface
triggered the segmentation violationsource->fd == 1701013878
which is insaneDescription:
sway
mpv
an indeterminate, seemingly random number of timessway
eventually crashes, sending me back to Linux terminalI will try to reproduce the issue with full debugging log and using a default configuration later tonight by running:
Will update this issue with the details if successful.
The text was updated successfully, but these errors were encountered: