Closed Bug 315934 Opened 19 years ago Closed 18 years ago

Crash on composing new mail [@ 0x04c2ffff b123a3b3] [@ js_GetSlotThreadSafe]

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 316543

People

(Reporter: gerard-majax, Unassigned)

Details

(Keywords: crash)

Crash Data

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20051104 SeaMonkey/1.1a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20051104 SeaMonkey/1.1a

When opening mail compose window (such as by clicking the compose button or reply, or forward ...), Seamonkey crashes instantly.

Reproducible: Always

Steps to Reproduce:
1. Start Seamonkey
2. Start mailnews
3. Click "compose".

Actual Results:  
Crash instantly. TalkBack send report.

Expected Results:  
No crash :)

Occures with a freshly created profile.
Misfilled bug, it happends with freshly new SeaMonkey 1.5a 20051110 Build. Not 1.1a 20051104 Build

Also, you might take a look at the TalkBack report http://moz-fr.infos-du-net.com/pub/mailnews-compose-crash-20051110.txt .
Version: unspecified → Trunk
xref bug 315560, but its dupe bug 315453 was reported fixed for 11/09 and I'm not seeing a problem with TB 1.6a1-1109, so it's probably not the *same* bug.
Alexandre, the stack you linked to is not really a stack. Could you install with talkback enabled and get a talkback ID? http://kb.mozillazine.org/Talkback
Keywords: crash
So, I take a look at talkback reports, as suggested on #seamonkey, and talkback reports are, as far as I think, http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=11691540
http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=11691914

So, talkback ID 11691540 and 11691914 ?
Keywords: talkbackid
reproduced again with 20051114 nightly.

TalkBack ID is TB11841826Y
Installed 2005111409 with Win32 Installer, no problem ?!
TB11841826Y is a separate crash. Could you file another bug for that?

Incident ID: 11691540
Stack Signature	0x04c2ffff b123a3b3
Product ID	MozillaTrunk
Build ID	2005111009
Trigger Time	2005-11-10 14:15:07.0
Platform	Win32
Operating System	Windows NT 5.0 build 2195
Module	
URL visited	
User Comments	
Since Last Crash	149 sec
Total Uptime	479 sec
Trigger Reason	Access violation
Source File, Line No.	N/A
Stack Trace 	
0x04c2ffff
js_GetSlotThreadSafe  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/js/src/jslock.c, line 592]
js_FindConstructor  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/js/src/jsobj.c, line 2058]
GetClassPrototype  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/js/src/jsobj.c, line 3802]
js_NewObject  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/js/src/jsobj.c, line 1950]
js_NewFunction  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/js/src/jsfun.c, line 1980]
JS_NewFunction  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/js/src/jsapi.c, line 3390]
XPCNativeMember::Resolve  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/js/src/xpconnect/src/xpcwrappednativeinfo.cpp, line 181]
DefinePropertyIfFound  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/js/src/xpconnect/src/xpcwrappednativejsops.cpp, line 448]
XPC_WN_NoHelper_Resolve  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/js/src/xpconnect/src/xpcwrappednativejsops.cpp, line 736]
js_LookupPropertyWithFlags  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/js/src/jsobj.c, line 2722]
js_LookupProperty  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/js/src/jsobj.c, line 2580]
js_GetProperty  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/js/src/jsobj.c, line 2865]
js_Interpret  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/js/src/jsinterp.c, line 5249]
js_Execute  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/js/src/jsinterp.c, line 1424]
JS_EvaluateUCScriptForPrincipals  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/js/src/jsapi.c, line 4102]
nsJSContext::EvaluateString  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/dom/src/base/nsJSEnvironment.cpp, line 1072]
nsGlobalWindow::RunTimeout  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/dom/src/base/nsGlobalWindow.cpp, line 6201]
nsGlobalWindow::TimerCallback  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/dom/src/base/nsGlobalWindow.cpp, line 6572]
nsAppStartup::Run  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/components/startup/src/nsAppStartup.cpp, line 208]
main  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1737]
WinMain  [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1761]
KERNEL32.dll + 0x28989 (0x77e98989)
Keywords: talkbackid
Summary: Crash on composing new mail → Crash on composing new mail [@ 0x04c2ffff b123a3b3] [@ js_GetSlotThreadSafe]
Dunno why I should open a new bug, it happens doing the same ..

*** This bug has been marked as a duplicate of 318121 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Adam, the stack at the bug you claim is a dupe doesn't match the stack here.
Am I missing something?
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
I see this on SeaMonkey on Linux (SUSE 10.1) on build 2002051405.
Every time I try to compose mail SeaMonkey crashes. There seems to be no talkback enabled on this build.
Status: UNCONFIRMED → NEW
Ever confirmed: true
James Rome, there's no telling if you're seeing the same crash unless you have a stack. See the Linux section on this page for info on how you might get one: http://kb.mozillazine.org/Talkback.
I am not up to compiling SeaMonkey myself with debugging installed. I have a talkback.xpi in the components directory. Can I use that somehow?

I upgraded to 1.5 because composing also stopped working. The compose window refused to let me enter the To: address or any message!

I do not see these problems on Windows.
Hmm... talkback.xpi is the packaged Talkback extension. You should have a talkback@mozilla.org folder. Maybe come on IRC (irc.mozilla.org) and join #seamonkey and see what those guys say about Talkback in recent SM builds?
I no longer have that version of SUSE installed. But yes, SeaMonkey was unusable then. It works for me now.
dup of bug 316543 ?
Alexandre LISSY, reporter is gone
but WFM per James

duping to bug 316543 where patch was checked in 2006-06-15 
Status: NEW → RESOLVED
Closed: 19 years ago18 years ago
Resolution: --- → DUPLICATE
Crash Signature: [@ 0x04c2ffff b123a3b3] [@ js_GetSlotThreadSafe]
You need to log in before you can comment on or make changes to this bug.