Re: jsdIDebuggerService crashing FF 2.0

On Dec 12, 6:56 pm, "John J. Barton" <[email protected]>
wrote:
> >   - talkback report IDs from the crashes.Here is the most recent four of about 30:
> TB27213209K, TB27213184Y, TB27211396E, TB27211391G
> what can be done with these?

start by visiting http://talkback-public.mozilla.org/search/start.jsp

Note that as of this writing talkback doesn't seem to be very
responsive, so be patient, or try again another day. You can search by
id, and you'll get a stack trace.

>From there, search for the signature in bugzilla.mozilla.org,
https://bugzilla.mozilla.org/query.cgi

If you don't find a bug, please file one. include the keyword 'crash',
[@ sign::nature] in the summary, and the stack trace in the
description.

you can also visit irc.mozilla.org and ask for help chasing it. problem
you'll end up talking to James Ross, or myself (but please don't expect
us to be around on weekends. sometimes we sleep and such).

Unfortunately, your first stack looks like this:
Incident ID: 27213209
Stack Signature	js_MarkGCThing 19bb9def
Product ID	Firefox2
Build ID	2006101023
Trigger Time	2006-12-11 22:02:56.0
Platform	Win32
Operating System	Windows NT 5.1 build 2600
Module	js3250.dll + (0001f26c)
URL visited
User Comments	jsds.on()
Since Last Crash	16 sec
Total Uptime	3891028 sec
Trigger Reason	Access violation
Source File, Line
No.	c:/builds/tinderbox/Fx-Mozilla1.8-release/WINNT_5.2_Depend/mozilla/js/src/jsgc.c,
line 2351
Stack Trace
js_MarkGCThing  [mozilla/js/src/jsgc.c, line 2351]
MarkGCThingChildren  [mozilla/js/src/jsgc.c, line 1971]
js_MarkGCThing  [mozilla/js/src/jsgc.c, line 2352]
js_GC  [mozilla/js/src/jsgc.c, line 2745]
JS_GC  [mozilla/js/src/jsapi.c, line 1944]
nsAppStartup::Run
[mozilla/toolkit/components/startup/src/nsAppStartup.cpp, line 152]
main  [mozilla/browser/app/nsBrowserApp.cpp, line 61]
kernel32.dll + 0x16fd7 (0x7c816fd7)

Which is useless. it just means that there's an object that probably
reached the dead state while something had a reference to it. In
general stacks with JS_GC in them are not very easy to solve (ideally
you manage to create a very simple reproducable testcase, and then
build a debug build and spend a long time learning about spidermonkey).

Note that not all crashes are the same, so while [@ js_MarkGCThing]
would be the signature, and while the stack probably matches a dozen
bugs, if the bugs don't talk about using jsd to trigger it, it's
/probably/ not the bug you want, and if you don't find a match that
does mention jsd/venkman/firebug, you'd want to use a new one.

Certainly if there's a change that you made to avoid the crash,
explaining (and providing sample code for crashing/simple change that
doesn't crash code) that's usually very helpful.