GNOME Bugzilla – Bug 780573
random crash (SIGABRT)
Last modified: 2021-06-19 08:47:46 UTC
Created attachment 348765 [details] gdb backtrace of the crash I am using eog 3.20.5-1+b1 with GNOME 3.22 on Debian stretch. I don't know exactly how I managed to crash eog and I can't reproduce it right now but it was while I was viewing this screenshot from dropbox. If the below backtrace summary and the attached full backtrace aren't useful, please close this bug. https://www.dropbox.com/s/hf5x3p9bne3tqbg/Screen%20Shot%202017-03-08%20at%2008.20.36.png?dl=1 Core was generated by `eog /tmp/user/1000/Screen Shot 2017-03-08 at 08.20.36.png'. Program terminated with signal SIGABRT, Aborted.
+ Trace 237292
I can't reproduce it either, at least from the image file alone. The weird part is the assertion it trips over indicated that the image has loaded already once. Maybe it's a problem which is triggered by how the Dropbox client syncs the file. Was it the only image in that folder? Do you have any plugins activated which might trigger image loading, e.g. for metadata?
The Drobox client wasn't involved, I downloaded it using my browser. I didn't keep a record of other files in that folder, so there could have been some more images or not. The only plugin I have enabled is "Fullscreen with double-click".
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/eog/-/issues/ Thank you for your understanding and your help.