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
Nemo consistently crashes with a SIGSEGV when an open folder gets heavily modified. For example, this happens if the open folder contains a large LaTeX project with several output files: after a few compilations where all the files are updated, nemo crashes in a very reproducible way. Occasionally, even if nemo is not open in such folder, going there after large modifications will trigger the SIGSEGV eventually.
System:
Ubuntu 14.04.3 with kernel 4.2.0-18-generic
Nemo:
version 2.8.6 from WebUpd8 PPA (no cinnamon dependencies)
I'm aware of my out-of-standard nemo installation, and since such folder is within MEGA, its extension may be the culprit, but maybe it's a nemo bug, I can't tell... Full backtrace is attached. gdb.txt
The text was updated successfully, but these errors were encountered:
diegobersanetti
changed the title
Reproducible SIGSEGV under high activity
Reproducible SIGSEGV if a large number of files gets modified
Nov 30, 2015
Nemo consistently crashes with a SIGSEGV when an open folder gets heavily modified. For example, this happens if the open folder contains a large LaTeX project with several output files: after a few compilations where all the files are updated, nemo crashes in a very reproducible way. Occasionally, even if nemo is not open in such folder, going there after large modifications will trigger the SIGSEGV eventually.
System:
Ubuntu 14.04.3 with kernel 4.2.0-18-generic
Nemo:
version 2.8.6 from WebUpd8 PPA (no cinnamon dependencies)
Installed packages:
nemo
nemo-compare
nemo-data
nemo-dbg
nemo-dropbox
nemo-fileroller
nemo-megasync
nemo-pushbullet
I'm aware of my out-of-standard nemo installation, and since such folder is within MEGA, its extension may be the culprit, but maybe it's a nemo bug, I can't tell... Full backtrace is attached.
gdb.txt
The text was updated successfully, but these errors were encountered: