Here's what I did: Go to http://news.com Resize the window wider a few times. Click the Bonsai button on the toolbar. It crashed, here's the stack trace (sorry it's not a debug build): #0 0x40660c0c in __pthread_mutex_lock (mutex=0x33) at mutex.c:95 #1 0x40642788 in PR_Lock (lock=0x33) at ptsynch.c:167 #2 0x4057142c in js_LockScope1 () #3 0x40571513 in js_LockObj () #4 0x40578013 in js_SetProperty () #5 0x4056b272 in js_Interpret () #6 0x40569bac in js_Invoke () #7 0x4056f696 in js_Interpret () #8 0x40569bac in js_Invoke () #9 0x40569d51 in js_CallFunctionValue () #10 0x4055483d in JS_CallFunctionValue () #11 0x40513893 in nsJSEventListener::ProcessEvent () #12 0x4035dfd1 in nsEventListenerManager::HandleEvent () #13 0x40a511ef in RDFElementImpl::HandleDOMEvent () #14 0x40a5121e in RDFElementImpl::HandleDOMEvent () #15 0x4035f00d in nsEventStateManager::CheckForAndDispatchClick () #16 0x4035ea8c in nsEventStateManager::PostHandleEvent () #17 0x4038171a in PresShell::HandleEvent () #18 0x40b4aff6 in nsView::HandleEvent () #19 0x40b4af9d in nsView::HandleEvent () #20 0x40b4af9d in nsView::HandleEvent () #21 0x40b4d7cc in nsScrollingView::HandleEvent () #22 0x40b4af9d in nsView::HandleEvent () #23 0x40b50c89 in nsViewManager::DispatchEvent () #24 0x40b49ade in HandleEvent () #25 0x4006e76e in nsWidget::DispatchEvent () #26 0x4006e6a5 in nsWidget::DispatchWindowEvent () #27 0x4006e7eb in nsWidget::DispatchMouseEvent () #28 0x4006c404 in handle_button_release_event () #29 0x40768c49 in gtk_marshal_BOOL__POINTER () #30 0x4072a915 in gtk_handlers_run () #31 0x40729c8e in gtk_signal_real_emit () #32 0x40727c5f in gtk_signal_emit () #33 0x4075f928 in gtk_widget_event () #34 0x406fb5e2 in gtk_propagate_event () #35 0x406fa768 in gtk_main_do_event () #36 0x407a4c8b in gdk_event_dispatch () #37 0x407d2dd2 in g_main_dispatch () #38 0x407d33bb in g_main_iterate () #39 0x407d3571 in g_main_run () #40 0x406fa15b in gtk_main () #41 0x40066929 in nsAppShell::Run () #42 0x4001253e in nsAppShellService::Run () #43 0x804a0f6 in main () I've tried, but I *can't* reproduce this. Since it's a pthread crash, could it be some kind of race condition?

Scott, do we have the thread version enabled on current SeaMonkey builds?

Yes, JS is built with thread-safety, but apparently not on all platforms. This was a topic of discussion over the last couple of days. It sounds like JS_THREADSAFE needs to be set because of some multithreaded work that Doug Turner is doing, but I don't think it's set on Windows or Mac yet. The stacktrace for this crash looks like a garbage lock is being passed in, which probably means the JSObject used is corrupted or has been GC'ed (because it wasn't properly rooted by the application). My guess is that the crash has nothing to do with thread-safety.

I am unable to reproduce this with today's build, though there was no "Bonsai button on the toolbar", as described in the report, so I was forced to type the URL into the location bar.

So, cegle, is this fixed now? Does this occur on all platforms?

The Bonsai button isn't there anymore. Typed URL into location bar on 5/10 build and the described failure didn't happen. Status changed to Verified.

Changing component to "Javascript Engine". "Javascript" component is being retired.