Bug 573107

Created attachment 399746 [details]
File: backtrace

#2  <signal handler called>
No symbol table info available.
#3  PresShell::ProcessReflowCommands (this=0x7fd90853c000, aInterruptible=1)
    at nsPresShell.cpp:6816
        idx = <value optimized out>
        scriptBlocker = {<No data fields>}
        deadline = 1400817868
#4  0x0000003aed0188ca in PresShell::DoFlushPendingNotifications (this=
    0x7fd90853c000, aType=Flush_Layout, aInterruptibleReflow=1)
    at nsPresShell.cpp:4870
        kungFuDeathGrip = {<nsCOMPtr_base> = {mRawPtr = 
    0x7fd90853c000}, <No data fields>}
        batch = {mRootVM = {<nsCOMPtr_base> = {mRawPtr = 
    0x7fd90a322af0}, <No data fields>}}
        updateFlags = <value optimized out>
        isSafeToFlush = 1
        viewManagerDeathGrip = {<nsCOMPtr_base> = {mRawPtr = 
    0x7fd90a322af0}, <No data fields>}
#5  0x0000003aed27cca3 in nsViewManager::DispatchEvent (this=0x7fd90a322af0, 
    aEvent=0x7fffea17ab30, aStatus=<value optimized out>)
    at nsViewManager.cpp:1137
        batch = {mRootVM = {<nsCOMPtr_base> = {mRawPtr = 
    0x7fd90a322af0}, <No data fields>}}
        observer = 0x7fd90853c0d8
        widget = <value optimized out>
        transparentWindow = <value optimized out>
        didResize = 0
        event = 0x7fffea17ab30
        view = 0x7fd908598e00
        region = {<nsCOMPtr_base> = {mRawPtr = 
    0x7fd8fb1b7920}, <No data fields>}
#6  0x0000003aed2786d9 in HandleEvent (aEvent=0x7fffea17ab30)
    at nsView.cpp:168
        vm = {<nsCOMPtr_base> = {mRawPtr = 0x7fd90a322af0}, <No data fields>}
        result = nsEventStatus_eConsumeNoDefault
        view = <value optimized out>
#7  0x0000003aed5f87d1 in nsWindow::DispatchEvent (this=0x7fd90862e680, 
    aEvent=<value optimized out>, aStatus=@0x7fffea17acb8) at nsWindow.cpp:577
No locals.



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

*** Bug 567426 has been marked as a duplicate of this bug. ***

Reporter, if you are willing, we need two things from you:

First, please post the output of the following command here as an attachment

 $ rpm -qa *xulrun* *firefox* *mozilla* *flash* *plugin*

Second, could you please elaborate more on your steps to reproduce?
Does the crash happen when you first open the page? After you run the test? At what point? Every time? Only once?

I am unable to verify the crash. I went to the broadband.gov site and ran the test from the flash popup without crashing, so we have to have more steps about whether this was a one-time crash, or ?



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

*** Bug 573869 has been marked as a duplicate of this bug. ***

*** Bug 571114 has been marked as a duplicate of this bug. ***

*** Bug 575223 has been marked as a duplicate of this bug. ***

Comment
-----
I don't know whether this particular segfault is reproducible.  With several other tabs open for other sites, I opened and began reading www.gmp.com.  Segfault occurred about 5 to 10 seconds after loading the page.

Without a site which we can use to successfully reproduce this crash, it is impossible to troubleshoot as is. We also need to know the versions of the software loaded shown by the command in comment 4.



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

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

I don't know if the original reporter has the exact same setup as us, but seeing as our ticket got closed as a duplicate of this one, here's hoping this will be of some use:

purple-plugin_pack-2.4.0-4.fc12.x86_64
yum-plugin-auto-update-debug-info-1.1.26-1.fc12.noarch
gstreamer-plugins-bad-free-0.10.18-1.fc12.x86_64
nspluginwrapper-1.3.0-10.fc12.i686
anaconda-yum-plugins-1.0-5.fc12.noarch
purple-plugin_pack-pidgin-2.4.0-4.fc12.x86_64
totem-mozplugin-2.28.5-1.fc12.x86_64
plymouth-plugin-two-step-0.8.0-0.2009.29.09.19.3.fc12.x86_64
abrt-plugin-logger-1.0.8-2.fc12.x86_64
alsa-plugins-pulseaudio-1.0.22-1.fc12.x86_64
nspluginwrapper-1.3.0-10.fc12.x86_64
gstreamer-plugins-base-0.10.28-1.fc12.x86_64
plymouth-plugin-label-0.8.0-0.2009.29.09.19.3.fc12.x86_64
abrt-plugin-runapp-1.0.8-2.fc12.x86_64
flash-plugin-10.0.45.2-release.i386
java-1.6.0-openjdk-plugin-1.6.0.0-36.b17.fc12.x86_64
mozilla-filesystem-1.9-5.fc12.x86_64
xulrunner-1.9.1.8-1.fc12.x86_64
gstreamer-plugins-good-0.10.21-1.fc12.x86_64
PackageKit-gstreamer-plugin-0.5.7-1.fc12.x86_64
PackageKit-yum-plugin-0.5.7-1.fc12.x86_64
setroubleshoot-plugins-2.1.40-1.fc12.noarch
abrt-plugin-bugzilla-1.0.8-2.fc12.x86_64
firefox-3.5.8-1.fc12.x86_64
xulrunner-devel-1.9.1.8-1.fc12.x86_64
report-plugin-bugzilla-0.8-1.fc12.x86_64
alsa-plugins-pulseaudio-1.0.22-1.fc12.i686
gdm-plugin-fingerprint-2.28.2-2.fc12.x86_64

*** Bug 578928 has been marked as a duplicate of this bug. ***

*** Bug 579374 has been marked as a duplicate of this bug. ***

Comment
-----
Don't know what happened and could not reproduce it...

All of the bugs that were marked as dupes had either exactly the same back-trace, or close enough that I am pretty decently sure that the crash is the same. If any of you know what, exactly, you were doing (what url, video, etc) when this crash occurred, our developer needs this information to attempt to recreate the crash on his test system.



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

*** Bug 556113 has been marked as a duplicate of this bug. ***

*** Bug 583418 has been marked as a duplicate of this bug. ***

*** Bug 584608 has been marked as a duplicate of this bug. ***

*** Bug 583696 has been marked as a duplicate of this bug. ***

*** Bug 584454 has been marked as a duplicate of this bug. ***

*** Bug 589339 has been marked as a duplicate of this bug. ***

*** Bug 590155 has been marked as a duplicate of this bug. ***

*** Bug 591274 has been marked as a duplicate of this bug. ***

The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. 
Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report.

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