Bug 1040209

Summary: [abrt] firefox-25.0-3.fc19: ~nsAutoPtr: Process /usr/lib/firefox/firefox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Doug Huffman <doug.huffman1>
Component: firefoxAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: chrisa, gecko-bugs-nobody
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/07417e2aaa8d60fbfaf6a6e9e86f8216fe907c0a
Whiteboard: abrt_hash:c72a7d248c506f23edf4b69139b21c9bfaef1ba6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-11 17:12:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Doug Huffman 2013-12-10 23:30:57 UTC 
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
Comment 1 Doug Huffman 2013-12-10 23:31:07 UTC 
Created attachment 834987 [details]
File: backtrace
Comment 2 Doug Huffman 2013-12-10 23:31:10 UTC 
Created attachment 834988 [details]
File: cgroup
Comment 3 Doug Huffman 2013-12-10 23:31:14 UTC 
Created attachment 834989 [details]
File: core_backtrace
Comment 4 Doug Huffman 2013-12-10 23:31:16 UTC 
Created attachment 834990 [details]
File: dso_list
Comment 5 Doug Huffman 2013-12-10 23:31:18 UTC 
Created attachment 834991 [details]
File: environ
Comment 6 Doug Huffman 2013-12-10 23:31:20 UTC 
Created attachment 834992 [details]
File: exploitable
Comment 7 Doug Huffman 2013-12-10 23:31:22 UTC 
Created attachment 834993 [details]
File: limits
Comment 8 Doug Huffman 2013-12-10 23:31:24 UTC 
Created attachment 834994 [details]
File: maps
Comment 9 Doug Huffman 2013-12-10 23:31:29 UTC 
Created attachment 834995 [details]
File: open_fds
Comment 10 Doug Huffman 2013-12-10 23:31:30 UTC 
Created attachment 834996 [details]
File: proc_pid_status
Comment 11 Doug Huffman 2013-12-10 23:31:33 UTC 
Created attachment 834997 [details]
File: var_log_messages
Comment 12 Martin Stransky 2013-12-11 17:12:18 UTC 
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!
Comment 13 Christopher Archer 2013-12-16 19:12:18 UTC 
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.