Hide Forgot
Description of problem: Just browsing. Version-Release number of selected component: firefox-25.0-3.fc19 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/lib/firefox/firefox crash_function: ~nsAutoPtr executable: /usr/lib/firefox/firefox kernel: 3.11.10-200.fc19.i686.PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 ~nsAutoPtr at ../../dist/include/nsAutoPtr.h:77 #1 ~CacheHashEntry at /usr/src/debug/xulrunner-25.0/mozilla-release/gfx/thebes/gfxFont.h:1883 #2 nsTHashtable<gfxFont::CacheHashEntry>::s_ClearEntry at ../../dist/include/nsTHashtable.h:464 #3 PL_DHashTableRawRemove at /usr/src/debug/xulrunner-25.0/mozilla-release/objdir/xpcom/build/pldhash.cpp:682 #4 PL_DHashTableEnumerate at /usr/src/debug/xulrunner-25.0/mozilla-release/objdir/xpcom/build/pldhash.cpp:716 #5 Clear at ../../dist/include/nsTHashtable.h:248 #6 gfxFont::ClearCachedWords at /usr/src/debug/xulrunner-25.0/mozilla-release/gfx/thebes/gfxFont.h:1686 #7 gfxFontCache::NotifyExpired at /usr/src/debug/xulrunner-25.0/mozilla-release/gfx/thebes/gfxFont.cpp:1462 #8 nsExpirationTracker<gfxFont, 3u>::AgeOneGeneration at ../../dist/include/nsExpirationTracker.h:188 #9 nsExpirationTracker<gfxFont, 3u>::TimerCallback at ../../dist/include/nsExpirationTracker.h:311
Created attachment 834987 [details] File: backtrace
Created attachment 834988 [details] File: cgroup
Created attachment 834989 [details] File: core_backtrace
Created attachment 834990 [details] File: dso_list
Created attachment 834991 [details] File: environ
Created attachment 834992 [details] File: exploitable
Created attachment 834993 [details] File: limits
Created attachment 834994 [details] File: maps
Created attachment 834995 [details] File: open_fds
Created attachment 834996 [details] File: proc_pid_status
Created attachment 834997 [details] File: var_log_messages
This is an automatic bug processing. If you can reproduce the crash (or see it regularly) please reopen the bug and remove [abrt] from the subject. Thanks!
This is happening regularly on one of my home machines. Trigger is unclear (it's used mostly by my wife) and seems to have started only recently, within the last 3 days or so. ABRT always catches the crash and attempts to report, so I'm not sure why ABRT should be removed from the subject.