abrt version: 1.1.10
Attached file: backtrace
reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Red Hat Enterprise Linux Workstation release 6.0 Beta (Santiago)
Created attachment 433227 [details]
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
#3 <signal handler called>
No symbol table info available.
#4 0x06f9f4f9 in nsCOMPtr_base::~nsCOMPtr_base (this=<value optimized out>,
__in_chrg=<value optimized out>) at nsCOMPtr.cpp:81
#5 0x06877177 in RemoveUndisplayedEntry (he=0xa3bf0a80, i=35, arg=0x0)
node = 0xa3bf0a70
#6 0x060b34c9 in PL_HashTableEnumerateEntries (ht=0xa2efcd40,
f=0x6877154 <RemoveUndisplayedEntry(PLHashEntry*, PRIntn, void*)>,
arg=0x0) at ../../mozilla/nsprpub/lib/ds/plhash.c:406
he = 0xa3bf0a80
hep = <value optimized out>
i = <value optimized out>
nbuckets = 128
rv = <value optimized out>
n = 35
todo = 0xa3ae4a80
#7 0x0687712f in nsFrameManagerBase::UndisplayedMap::Clear (this=0x9b7ef0c0)
#8 0x0687746e in nsFrameManagerBase::UndisplayedMap::~UndisplayedMap (
this=0x9b7ef0c0, __in_chrg=<value optimized out>)
#9 0x0687870c in nsFrameManager::Destroy (this=0xa0c1e33c)
#10 0x068904df in PresShell::Destroy (this=0xa0c1e320) at nsPresShell.cpp:1949
Please, describe the steps that led to this issue and how to reproduce it. What settings, networks, or configurations are needed to reproduce the issue?
Thank you for your bug report. This issue was evaluated for inclusion
in the current release of Red Hat Enterprise Linux. Unfortunately, we
are unable to address this request in the current release. Because we
are in the final stage of Red Hat Enterprise Linux 6 development, only
significant, release-blocking issues involving serious regressions and
data corruption can be considered.
If you believe this issue meets the release blocking criteria as
defined and communicated to you by your Red Hat Support representative,
please ask your representative to file this issue as a blocker for the
current release. Otherwise, ask that it be evaluated for inclusion in
the next minor release of Red Hat Enterprise Linux.
hey Matej, this was just during normal use. What specifically are you interested in?
(In reply to comment #7)
> hey Matej, this was just during normal use. What specifically are you
> interested in?
Well in order to analyze this bug we need some how to reproduce it. Do you have any idea what specific steps may lead to this crash? What settings, networks, or configurations are needed to reproduce the issue?
unfortunately, I have no clue how to reproduce, sorry.
Since there are insufficient details provided in this report for us to investigate the issue further, we are not able to reproduce the problem, and we cannot analyze it further.
Closing as INSUFFICIENT_DATA.