302682 - FireFox crashes after viewing the printable version of the Wikipedia main page and pressing the back button [@ 0x02241ce3][@ nsAttributeTextNode::DetachListener]

Status: RESOLVED WORKSFORME

(Core :: DOM: Core & HTML, defect)

Description

[Craig Presnell]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

Viewing the printable version of the Wikipedia Main Page at
http://en.wikipedia.org/wiki/Main_Page then returning to the normal skin causes
FireFox to crash everytime.

Reproducible: Always

Steps to Reproduce:
1. Go to the Wikipedia Main Page at http://en.wikipedia.org/wiki/Main_Page
2. At the 'toolbox' on the left column, select 'Printable Version'
3. Press the back button

Actual Results:  
FireFox crashed.

Expected Results:  
Redisplay the Wikipedia main page in the standard 'skin'.

I did use the quality agent to send data after the crash but did not see a
reference number after the report was sent. The report could be cross-referenced
against my email address if needed.

Comment 1

[Dave Townsend [:mossop]]

Run the talkback program from the components directory in the firefox
installation directory to see the talkback IDs

Comment 2

[Craig Presnell]

Thanks Dave, the Incident ID is TB7922760Z.

Comment 3

[timeless]

strange, are you using any extensions, and can you try sending a couple of
additional talkback reports, for reference, i'm pulling the following
information from
http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=TB7922760Z
you can use that webpage to try it with your new incident ids.

Incident ID: 7922760
Stack Signature	0x02241ce3 0fbbee6e
Product ID	Firefox10
Build ID	2005071605
Trigger Time	2005-07-29 12:58:13.0
Platform	Win32
Operating System	Windows NT 5.1 build 2600
Module	
URL visited	http://en.wikipedia.org/wiki/Main_Page
User Comments	1) Was at the Wikipedia main page -
http://en.wikipedia.org/wiki/Main_Page 2) Clicked "Printable Version" 3) Pressed
the back button Then firefox crashed. *** THIS PROBLEM IS 100% REPEATABLE ***
Since Last Crash	64 sec
Total Uptime	435343 sec
Trigger Reason	Access violation
Source File, Line No.	N/A
Stack Trace 
0x02241ce3
0x986030d2

does this happen w/ trunk?

Comment 4

[Craig Presnell]

I've generated two additional talkback reports:

1) TB7941693Z
http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=TB7941693Z

2) TB7941719H
http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=TB7941719H

I have 2 extensions installed:

1) adblock v.5 d2 * nightly 39
- I doubled checked my filter list and didn't see any references to wikipedia

2) mozimage 1.2.0

(sorry - I'm not sure what you mean by 'trunk' but if there's any other data I
could collect, please let me know, and I'd be happy to get it)

Thanks, 

Craig

Comment 5

[Craig Presnell]

Just a quick followup: I tried the same steps to reproduce this problem on
several other Wikipedia articles and did not see a crash. It only happens on the
Main Page   (http://en.wikipedia.org/wiki/Main_Page).

Comment 6

[Jaime Mitchell (use [e-mail] for email)]

Craig, trunk is the current development version (what will become firefox 1.5),
you can download it from here:
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk

Incident ID: 7941719
Stack Signature	 0x002701b0 9c888385
Product ID	Firefox10
Build ID	2005071605
Trigger Time	2005-07-30 08:22:05.0
Platform	Win32
Operating System	Windows NT 5.1 build 2600
Module	
URL visited	http://en.wikipedia.org/wiki/Main_Page
User Comments	Gathering additional data (2/2) for Bug #302682
https://bugzilla.mozilla.org/show_bug.cgi?id=302682
Since Last Crash	27 sec
Total Uptime	504995 sec
Trigger Reason	Access violation
Source File, Line No.	N/A
Stack Trace 	
0x002701b0
nsAttributeTextNode::DetachListener 
[c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/content/base/src/nsTextNode.cpp,
line 356]
nsAttributeTextNode::~nsAttributeTextNode 
[c:/builds/tinderbox/Fx-Aviary1.0.1/WINNT_5.2_Depend/mozilla/content/base/src/nsTextNode.cpp,
line 117]

Incident ID: 7941693 is the same

Comment 7

[Frank Wein [:mcsmurf]]

Trunk build means the latest and greatest we have ;-) (remember FF 1.0.x was
split off from the main development trunk more than a year ago, so FF 1.0.x is
from a technical point of view quite old). You can get it under
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/ (either as
installer or as ZIP).

Comment 8

[Craig Presnell]

Jaime and Frank - Thanks for the information on the trunk version. I downloaded
the 7/30/05 version and installed it.

I could _not_ reproduce this problem with the trunk version after making several
attempts. I also went to several other wikipedia articles, tried the same thing,
and did not get a failure.

I also went back and double-checked that the problem still exists with my 1.0.6
install. 

Tomorrow I plan to try and reproduce this on two machines at work which have
recently been upgraded to 1.0.6 to see if I can rule out anything specific
regarding my configuration here.

Craig

Comment 9

[Craig Presnell]

I believe I have ruled out any configuration issues on my home machine as I was
able to reproduce this problem on two separate machines at work:

1) Toshiba A65-5126 laptop w/ WinXP Home
Talkback ID: TB7994974Z
http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=TB7994974Z

2) Dell GX240 desktop w/ WinXP Pro
Talkback ID: TB7995029G
http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=TB7995029G

[for reference, talkback reports prior to these two were generated on my home
machine, a Dell 1150 laptop w/ WinXP Home]

The interesting thing here is that the GX240 originally had Firefox 1.0.2
installed. I was _not_ able to reproduce the problem with this version. I could
only recreate it on this machine _after_ I upgraded to 1.0.6.

Based on the results gathered so far, it would appear the problem was introduced
after 1.0.2, definetely shows up in 1.0.6, but is fixed in the trunk version.

Craig

Comment 10

[Wayne Mery (:wsmwk)]

(In reply to comment #9)
> Based on the results gathered so far, it would appear the problem was introduced
> after 1.0.2, definetely shows up in 1.0.6, but is fixed in the trunk version.
> 
> Craig

WFM also (trunk) and marking bug so