425635 - crash [@0xacfed075] [@ nsAppShell::ProcessNextNativeEvent(int)] clicking on a link

Status: RESOLVED INCOMPLETE

(SeaMonkey :: General, defect)

Description

[Tony Mechelynck [:tonymec]]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9pre) Gecko/2008032701 SeaMonkey/2.0a1pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9pre) Gecko/2008032701 SeaMonkey/2.0a1pre

Browsing page http://www.uea.org/kongresoj/uk_2008.html
In section "... mendi hotelon, ekskursojn kaj aliajn servojn?" I clicked the link "La reta mendilo (nur por la jamaj aliĝintoj)" and SeaMonkey crashed: bp-2506e7fa-fcad-11dc-8adb-001a4bd43e5c

Reproducible: Didn't try

Steps to Reproduce:
1. See details above

Actual Results:  
crash

Expected Results:  
no crash; possibly a popup asking for member ID and/or congress membership ID

Additional info: stack of crashing thread:

Frame  	Signature  	Source
0 	@0xacfed075 	
1 	libglib-2.0.so.0.1400.1@0x2fd45 	
2 	libglib-2.0.so.0.1400.1@0x2f5d5 	
3 	libglib-2.0.so.0.1400.1@0x32971 	
4 	libglib-2.0.so.0.1400.1@0x32f2d 	
5 	nsAppShell::ProcessNextNativeEvent(int) 	mozilla/widget/src/gtk2/nsAppShell.cpp:144
6 	nsBaseAppShell::DoProcessNextNativeEvent(int) 	mozilla/widget/src/xpwidgets/nsBaseAppShell.cpp:151
7 	nsBaseAppShell::OnProcessNextEvent(nsIThreadInternal*, int, unsigned int) 	mozilla/widget/src/xpwidgets/nsBaseAppShell.cpp:296
8 	libxpcom_core.so@0x5828f 	
9 	libxpcom_core.so@0x26d4a 	
10 	nsBaseAppShell::Run() 	mozilla/widget/src/xpwidgets/nsBaseAppShell.cpp:170
11 	nsAppStartup::Run() 	mozilla/toolkit/components/startup/src/nsAppStartup.cpp:181
12 	libxul.so@0x15a1e 	
13 	main 	
14 	libc-2.6.1.so@0x15fdf

Comment 1

[Tony Mechelynck [:tonymec]]

Bug seems solid: clicked the link again and it crashed again, bp-3d55da82-fcb5-11dc-8c94-001a4bd43ef6

Comment 2

[Andrew Schultz]

WFM.  it's crashing glib with nothing else interesting going on

Can you try older builds to see when this starting happening and/or reduce the page to a testcase?

Comment 3

[Tony Mechelynck [:tonymec]]

Attachment: multitab homepage (from prefs.js)

(In reply to comment #2)
> WFM.  it's crashing glib with nothing else interesting going on
> 
> Can you try older builds to see when this starting happening and/or reduce the
> page to a testcase?
> 

I haven't yet found an older build where I don't get this bug in the circumstances where I get it in the current nightly; but in "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9pre) Gecko/2008032801 SeaMonkey/2.0a1pre" I get the bug in my usual session of more than 30 tabs, but not if I open this URL in a new window.

I'm attaching the lines of prefs.js describing my multitab homepage. (A few of them are "file:" URIs but I hope it won't make a significant difference.)

I'm not sure how to go about reducing the testcase (I seem to have fattened it instead) -- can you crash Sm with this additional info?

Comment 4

[Tony Mechelynck [:tonymec]]

P.S. I don't crash if I click the URL link on top of this bug, but I do if I go to the page mentioned in comment #0 and click the mentioned link in that page.

Comment 5

[Andrew Schultz]

Do you also crash if you just reload the URL from comment 0?

Comment 6

[Tony Mechelynck [:tonymec]]

(In reply to comment #5)
> Do you also crash if you just reload the URL from comment 0?
> 

not the URL from comment #0 but, on that page http://www.uea.org/kongresoj/uk_2008.html , the link "La reta mendilo (nur por jamaj aliĝintoj)", which is supposed to link to http://www.uea.org/kongresoj/uk_mendilo.html

Comment 7

[Tony Mechelynck [:tonymec]]

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9pre) Gecko/2008041501 SeaMonkey/2.0a1pre

Had it again clicking that same link on that same page
bp-5e12f773-0b09-11dd-abe8-001cc4e2bf68
Except for the bogus top-of-stack (jump to uninitialized pointer?), the stack is the same.

The same link works OK in Konqueror 3.5.7
Mozilla 5.0 (compatible; Konqueror/3.5; Linux 2.6.22.17-0.1-default; X11; i686; en-US) KHTML/3.5.7 (like Gecko) SUSE

Comment 8

[kmike]

SM doesn't crash when I follow the steps described in comment #0, however I experience the random crashes every few days with the same stack. The latest is:
bp-30e1530c-3881-11dd-8eaa-0013211cbf8a

Mozilla/5.0 (X11; U; Linux i686; rv:1.9pre) Gecko/2008060301 SeaMonkey/2.0a1pre

Comment 9

[Wayne Mery (:wsmwk)]

Tony, are you able to reproduce using SM 2.x?

Comment 10

[Tony Mechelynck [:tonymec]]

(In reply to comment #9)
> Tony, are you able to reproduce using SM 2.x?

no but the page has changed: that congress (Rotterdam) happened in July 2008, the next one (Białystok) in July 2009, and I'm not going to Havana in 2010. I guess this bug can be RESOLVED WORKSFORME or even INCOMPLETE unless someone can come up with a similar crash (and, if possible, a testcase) for some current build.