Bug 583946 - [abrt] crash in firefox-3.5.9-2.fc12: Process /usr/lib64/firefox-3.5/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in firefox-3.5.9-2.fc12: Process /usr/lib64/firefox-3.5/firefox ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Martin Stransky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1bedc764496256d3f8eb8ea609f...
: 569292 573956 585883 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-20 10:25 UTC by Louis van Dyk
Modified: 2010-12-03 15:39 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-03 15:39:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (87.43 KB, text/plain)
2010-04-20 10:25 UTC, Louis van Dyk
no flags Details
This is the htm file that is opened when Firefox crashes. (3.27 KB, text/html)
2010-04-20 10:32 UTC, Louis van Dyk
no flags Details
Javascript in this file might be causing the crash. (6.13 KB, text/html)
2010-04-20 13:20 UTC, Louis van Dyk
no flags Details

Description Louis van Dyk 2010-04-20 10:25:42 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.5/firefox
comment: If I do the same thing on "Seamonkey (i386)" there is no crash.  Firmware revision : GF 
component: firefox
executable: /usr/lib64/firefox-3.5/firefox
kernel: 2.6.32.10-90.fc12.x86_64
package: firefox-3.5.9-2.fc12
rating: 4
reason: Process /usr/lib64/firefox-3.5/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. I opened the page to the UPS's management page.  Galaxy PW Single.  From APC Schneider
2. When I click on the "about your UPS" button, firefox crashes.
3.

Comment 1 Louis van Dyk 2010-04-20 10:25:50 UTC
Created attachment 407781 [details]
File: backtrace

Comment 2 Louis van Dyk 2010-04-20 10:27:43 UTC

How to reproduce
-----
1. Again opened the UPS page and clicked About Your UPS.
2. Same fault occurred.
3.

Comment 3 Louis van Dyk 2010-04-20 10:32:38 UTC
Created attachment 407782 [details]
This is the htm file that is opened when Firefox crashes.

This is the htm file that is opened when Firefox crashes.

Comment 4 Louis van Dyk 2010-04-20 13:05:15 UTC

How to reproduce
-----
1. I had the APC UPS Interface Web page open - and was browsing on other pages when it crashed.
2.
3.

Comment 5 Louis van Dyk 2010-04-20 13:05:57 UTC

How to reproduce
-----
1. I had the APC UPS Interface Web page open - and was browsing on other pages when it crashed.
2.
3.

Comment 6 Louis van Dyk 2010-04-20 13:14:45 UTC

How to reproduce
-----
1.  CORRECTION:  Open UPS Management page, and just leave it.  Firefox will crash.
2.  When opened on Seamonkey, there is an additional item appearing in the menu.
    "3-Phase Display" appears briefly then DISAPPEARS on the Firefox menu.  A little later the crash occurs.


Comment
-----
I will attach the "menu.htm" file.

Comment 7 Louis van Dyk 2010-04-20 13:20:09 UTC
Created attachment 407818 [details]
Javascript in this file might be causing the crash.

Javascript in this file may be causing the crash.  There are menu items which disappear and later firefox HANGS and CRASHES.

Comment 8 D. Wagner 2010-04-21 17:04:39 UTC

How to reproduce
-----
I don't know if this can be reproduced (haven't tested it yet).


Comment
-----
This is probably related to Java.

I went to http://netalyzr.icsi.berkeley.edu/, clicked Start Analysis, clicked OK on the popup to allow the Java applet to run, let it run for a while, read the results page for a while, then clicked back a few times to get back to the start page, and clicked Start Analysis again.  Then in a space of a few seconds: I clicked Cancel on the Java applet popup, clicked back and forward once or twice, and the browser froze briefly and then crashed.  So this might be related to clicking Cancel on the popup, or to the forward/back on pages containing Java applets.

Comment 9 Karel Klíč 2010-05-25 10:03:23 UTC
*** Bug 573956 has been marked as a duplicate of this bug. ***

Comment 10 Chris Campbell 2010-05-28 12:59:26 UTC
#2  <signal handler called>
No symbol table info available.
#3  GetURLRunnable::Run (this=0x7f2acaff5c40) at IcedTeaPlugin.cc:1478
        ownerGetter = {<nsCOMPtr_base> = {
            mRawPtr = 0x7f2acbf35df0}, <No data fields>}
        owner = 0x0
#4  0x00000036faec5b9b in nsThread::ProcessNextEvent (this=0x7f2af013b790, 
    mayWait=1, result=0x7ffff09a5258) at nsThread.cpp:521
        notifyGlobalObserver = 1
        obs = {<nsCOMPtr_base> = {mRawPtr = 0x7f2ae7f22048}, <No data fields>}
        event = {<nsCOMPtr_base> = {
            mRawPtr = 0x7f2acaff5c40}, <No data fields>}
        rv = 0
#5  0x00007f2ad73802c4 in IcedTeaPluginFactory::GetJavaObject (
    this=0x7f2aceafa360, instance_identifier=<value optimized out>, 
    object=<value optimized out>) at IcedTeaPlugin.cc:2825
        reference = 0
        container = <value optimized out>
        startTime = 1271753800
        objectMessage = {<nsCStringContainer> = {<nsACString> = {<No data fields>}, <nsStringContainer_base> = {d1 = 0x7f2acfb19be8, d2 = 37, 
              d3 = 5}, <No data fields>}, <No data fields>}
        processed = 1
        result = 0
#6  0x00007f2ad737e52c in IcedTeaPluginInstance::GetJavaObject (
    this=0x7f2acfcba860, object=0x7ffff09a5308) at IcedTeaPlugin.cc:2659
        _trace = {name = 0x7f2ad7395cbd "Instance::", 
          function = 0x7f2ad7398c9e "GetJavaObject"}
        __func__ = "GetJavaObject"
#7  0x00000036faaa952e in nsHTMLPluginObjElementSH::GetJavaPluginJSObject (
    cx=0x7f2acf920c00, obj=<value optimized out>, plugin_inst=0x7f2acfcba860, 
    plugin_obj=0x7ffff09a5498, plugin_proto=<value optimized out>)
    at nsDOMClassInfo.cpp:9662
        jvm = {<nsCOMPtr_base> = {mRawPtr = 0x7f2ad2723390}, <No data fields>}
        javaPluginInstance = {<nsCOMPtr_base> = {
            mRawPtr = 0x7f2acfcba868}, <No data fields>}
        rv = <value optimized out>
        manager = {<nsCOMPtr_base> = {
            mRawPtr = 0x7f2acfcba860}, <No data fields>}
        appletObject = 0x0



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 11 Chris Campbell 2010-05-28 13:00:36 UTC
*** Bug 569292 has been marked as a duplicate of this bug. ***

Comment 12 Chris Campbell 2010-05-28 13:01:05 UTC
*** Bug 585883 has been marked as a duplicate of this bug. ***

Comment 13 Chris Campbell 2010-05-28 13:01:35 UTC
This bug has been triaged



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 14 Bug Zapper 2010-11-03 16:43:47 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 15 Bug Zapper 2010-12-03 15:39:55 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.