Description of problem: Firefox. Trawling through old gmail. Saved an image of a lynx in a sink > crash. The image was saved to downloads. Version-Release number of selected component: firefox-46.0.1-4.fc24 Additional info: reporter: libreport-2.7.0 backtrace_rating: 4 cmdline: /usr/lib64/firefox/firefox crash_function: nsProfileLock::FatalSignalHandler executable: /usr/lib64/firefox/firefox global_pid: 3783 kernel: 4.5.5-300.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #1 nsProfileLock::FatalSignalHandler at /usr/src/debug/firefox-46.0.1/firefox-46.0.1/toolkit/profile/nsProfileLock.cpp:181 #3 compare_directory at gtkfilechooserwidget.c:4109 #4 name_sort_func at gtkfilechooserwidget.c:4192 #5 compare_array_element at gtkfilesystemmodel.c:766 #6 msort_with_tmp at gqsort.c:152 #9 msort_r at gqsort.c:237 #10 g_qsort_with_data at gqsort.c:303 #11 gtk_file_system_model_sort at gtkfilesystemmodel.c:790 #13 gtk_file_system_model_sort_node at gtkfilesystemmodel.c:833 #14 add_file at gtkfilesystemmodel.c:1869
Created attachment 1161796 [details] File: backtrace
Created attachment 1161797 [details] File: cgroup
Created attachment 1161798 [details] File: core_backtrace
Created attachment 1161799 [details] File: dso_list
Created attachment 1161800 [details] File: environ
Created attachment 1161801 [details] File: limits
Created attachment 1161802 [details] File: maps
Created attachment 1161803 [details] File: mountinfo
Created attachment 1161804 [details] File: namespaces
Created attachment 1161805 [details] File: open_fds
Created attachment 1161806 [details] File: proc_pid_status
Created attachment 1161807 [details] File: var_log_messages
Maintenance that landed Thursday morning appears to have fixed this problem. Most likely the resolution to https://bugzilla.redhat.com/show_bug.cgi?id=1339582 Closing as dup. Will reopen if problem returns. *** This bug has been marked as a duplicate of bug 1339582 ***