Bug 429657

Created attachment 292476 [details]
gecko bug report

You are right David, I see this also.

I have sent an error report via the firefox broken website reporting tool. I
have no idea what is causing this however.

Created attachment 292499 [details]
snecklifter gecko bug report

Ran through gdb with debuginfo packages installed. Received the following:

[New Thread -1275823216 (LWP 20093)]
[New Thread -1286890608 (LWP 20094)]
[New Thread -1297380464 (LWP 20095)]
[Thread -1297380464 (LWP 20095) exited]
[New Thread -1307870320 (LWP 20096)]
[Thread -1307870320 (LWP 20096) exited]
[New Thread -1307870320 (LWP 20097)]
[New Thread -1297380464 (LWP 20098)]
[New Thread -1320158320 (LWP 20099)]
[New Thread -1330648176 (LWP 20100)]
[Thread -1320158320 (LWP 20099) exited]
[Thread -1330648176 (LWP 20100) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208805680 (LWP 20082)]
0x012b6eba in nsGlobalWindow::GetScrollInfo (this=0xae9a558, 
    aScrollableView=0xbff378e0, aP2T=0xbff378dc, aT2P=0xbff378d8)
    at ../../../dist/include/layout/nsIPresShell.h:179
179       nsIViewManager* GetViewManager() { return mViewManager; }

Please let me know if you need any more information.

Cheers
Chris

Konqueror does not exhibit the issue. Epiphany does however:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208674528 (LWP 20332)]
0x01245eba in nsGlobalWindow::GetScrollInfo (this=0x8c19368, 
    aScrollableView=0xbfc00950, aP2T=0xbfc0094c, aT2P=0xbfc00948)
    at ../../../dist/include/layout/nsIPresShell.h:179
179       nsIViewManager* GetViewManager() { return mViewManager; }
Current language:  auto; currently c++

(In reply to comment #4)
> Please let me know if you need any more information.

Can you get a full stacktrace and add it as an attachment? 
http://fedoraproject.org/wiki/StackTraces#gdb

Created attachment 292561 [details]
snecklifter gdb stack trace

Had to run with:

gdb /usr/lib/firefox-2.0.0.10/firefox-bin

Let me know if this argument is incorrect. Stack Trace attached though it
didn't like:

thread apply all bt full

so you just have output from bt

Firefox on Windows spits the dummy as well.

Cheers
Chris

Possible duplicate of bug 407051?

(comparing to bug 407051 the crash is not in libflassupport)

At this point, we're going to only be taking security fixes and major stability
fixes into this release of Fedora.  However, we still want to ensure the bug is
fixed in the next version.  We'd appreciate if you could test Firefox 3,
available at http://www.mozilla.com/en-US/firefox/all-beta.html or now shipping
as the default in Fedora rawhide and provide feedback as to whether it still
exists so we can file a ticket upstream to try to fix it in Firefox 3 before it
is released.

At this point, we're going to only be taking security fixes and major stability
fixes into this release of Fedora.  However, we still want to ensure the bug is
fixed in the next version.  We'd appreciate if you could test Firefox 3,
available at http://www.mozilla.com/en-US/firefox/all-beta.html or now shipping
as the default in Fedora rawhide and provide feedback as to whether it still
exists so we can file a ticket upstream to try to fix it in Firefox 3 before it
is released.

It is no longer crashing for me on the above test. This is with the latest
Firefox though I suspect it is more a case of that website fixing their crappy
code...

David?

Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
information.

Closing as INSUFFICIENT_DATA.

[This is a mass-closing request, if you think that this bug shouldn't be closed,
please, reopen with additional information.]