621694 - Reproducable crash of venkman when stepping through js-functions

Status: RESOLVED DUPLICATE of bug 616899

(Other Applications Graveyard :: Venkman JS Debugger, defect)

Description

[Karsten]

User-Agent:       Opera/9.80 (Windows NT 5.1; U; de) Presto/2.7.62 Version/11.00
Build Identifier: 0.9.88.1

When debugging js-functions venkman crashes each time at the same line of code.
a older venkman (0.9.87.4) together with Firefox 3.0 works fine at the same code.

Reproducible: Always

Steps to Reproduce:
1. Starting of Firefox 3.6.13 (without loading a website)
2. Starting JavaSriptDebugger (from Extras-menu)
3. Loading and displaying the webpage 
   http://www.zeitgeschichte-hamburg.de/MEX_Internetdarstellung/Bestaendeuebersicht_A81026/index.htm
   I debugged the webpage with Firefox 3.0 together with venkman 0.9.87.4 on the first computer and at the same time on a second computer with Firefox 3.5 and venkman 0.9.88.1.
   I could do this on the first computer but not on the second.

4. Setting a breakpoint at dom.js, function XMLFactory, line 79
5. Refreshing the webpage with the refresh-button on the browser
6. ... results in "Stopped for breakpoint" at the venkman.
7. now I stepped through the next instructions and called funtions with [Step into]
   until I reach in the function "startConfig" the line 1278.

8. At this point venkman crashes - the different windows are going black 
   (except the Interactive Session - this one stays readable). No command input is possible
Actual Results:  
A series of screenshots during cras production is shon under the following link as a pdf file:
http://wsthh.de/Bug-Meldung venkman.pdf

Expected Results:  
Venkman should do the next steps

see the screenshots under
http://wsthh.de/Bug-Meldung venkman.pdf

Comment 1

[timeless]

https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report

Comment 2

[Karsten]

the reported stacktrace for this bug was
"http://crash-stats.mozilla.com/report/index/bp-d1f2d23a-2660-442a-bc42-a9d552101227". Sorry that I have forgotten totell it.
The link for the screenshot is 
"http://wsthh.de/Bug-Meldung venkman.pdf" including the blank!

Comment 3

[timeless]

Signature	nsTreeBodyFrame::PrefillPropertyArray(int, nsTreeColumn*)
UUID	d1f2d23a-2660-442a-bc42-a9d552101227
Time	2010-12-27 14:03:31.675629
Uptime	698
Last Crash	710 seconds (11.8 minutes) before submission
Install Age	606980 seconds (1.0 weeks) since version was first installed.
Product	Firefox
Version	3.6.13
Build ID	20101203075014
Branch	1.9.2
OS	Windows NT
OS Version	5.1.2600 Service Pack 2
CPU	x86
CPU Info	GenuineIntel family 15 model 4 stepping 3
Crash Reason	EXCEPTION_ACCESS_VIOLATION_READ
Crash Address	0xfffffffff0de800f
User Comments	
Processor Notes	
EMCheckCompatibility	False
Related Bugs

---
616899 UNCONFIRMED crash [@ nsTreeBodyFrame::PrefillPropertyArray(int, nsTreeColumn*)] when using the JavaScript debugger
615958 ASSIGNED crash [@ nsTreeBodyFrame::PrefillPropertyArray(int, nsTreeColumn*)]
Crashing Thread

Frame	Module	Signature [Expand]	Source
0	xul.dll	nsTreeBodyFrame::PrefillPropertyArray	layout/xul/base/src/tree/src/nsTreeBodyFrame.cpp:1983
1	xul.dll	nsTreeBodyFrame::PaintColumn	layout/xul/base/src/tree/src/nsTreeBodyFrame.cpp:2915
Show/hide other threads

https://developer.mozilla.org/En/How_to_get_a_stacktrace_with_windbg -- i'd like a better stack trace (and other stuff).

Please tag me on irc once you get to !analyze, before you quit the debugger, i basically want:

.frame 6 <- where 6 is the crashing frame, I can't guess offhand what it'll be
dv