43606 - Clicking button results in "JavaScript error: line 0:" (hangs UI)

Status: VERIFIED FIXED

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

Description

[Russell East]

I am using a DEBUG build using M16 source, that was only modified by the patch 
identified by bug 40160

When I visit this URL
   http://www.geographynetwork.com/explorer/geonet_explorer.cfm
then click the "Search" tab, 
I see this in the console:
  JavaScript error:
   line 0:
  Document: Done (55.17 secs)

I am expecting to see a new form but never see it - you can see it work using 
Netscape 6 or 4.7 no problem.

Comment 1

[John Morrison]

In a tip build (9pm jun22 linux), clicking on the 'Search' tab for 
this page hangs the UI thread (browser becomes unresponsive and no
longer repaints). When I break in the debugger, I get the stack 
trace below. 

Passing on to jst, cc: adamlock for docshell. Note that this site
is using a fair amount of JS/DHTML, and there is a bug filed 
(bug 43607) for a different problem (failing to load content in
one of the frames). 


(gdb) thread 2
[Switching to thread 2 (Thread 15456 (initial thread))]
#0  0x4056758b in __sigsuspend (set=0xbfffe3d8)
    at ../sysdeps/unix/sysv/linux/sigsuspend.c:48
48      in ../sysdeps/unix/sysv/linux/sigsuspend.c
(gdb) bt
#0  0x4056758b in __sigsuspend (set=0xbfffe3d8)
    at ../sysdeps/unix/sysv/linux/sigsuspend.c:48
#1  0x402ad211 in __pthread_lock (lock=0x8909a1c, self=0x402b36c0)
    at restart.h:32
#2  0x402aa99a in __pthread_mutex_lock (mutex=0x8909a0c) at mutex.c:84
#3  0x40288abb in PR_Lock (lock=0x8909a0c) at ptsynch.c:167
#4  0x402898ac in PR_EnterMonitor (mon=0x8909a08) at ptsynch.c:492
#5  0x40157dba in nsAutoMonitor::nsAutoMonitor (this=0xbfffe4d0, mon=0x8909a08)
    at nsAutoLock.h:184
#6  0x40e33645 in nsFileTransport::Cancel (this=0x8909978, status=2152398850)
    at nsFileTransport.cpp:190
#7  0x40e43378 in nsStreamIOChannel::Cancel (this=0x8874b98, status=2152398850)
    at nsInputStreamChannel.cpp:206
#8  0x40e41597 in nsLoadGroup::Cancel (this=0x8a30b98, status=2152398850)
    at nsLoadGroup.cpp:225
#9  0x418fc0e5 in nsDocLoaderImpl::Stop (this=0x8946300) at nsDocLoader.cpp:274
#10 0x418fa655 in nsURILoader::Stop (this=0x81ce948, aLoadCookie=0x8946318)
    at nsURILoader.cpp:607
#11 0x4030db13 in nsDocShell::StopLoad (this=0x87758a0) at nsDocShell.cpp:254
#12 0x40317e40 in nsDocShell::InternalLoad (this=0x87758a0, aURI=0x883b598, 
    aReferrer=0x88a6758, aOwner=0x0, aWindowTarget=0x0, aPostData=0x0, 
    aLoadType=1) at nsDocShell.cpp:2332
#13 0x4030d8ec in nsDocShell::LoadURI (this=0x87758a0, aURI=0x883b598, 
    aLoadInfo=0x8a025b0) at nsDocShell.cpp:231
#14 0x403bb3d2 in LocationImpl::SetHrefWithBase (this=0x88a5da8, 
    aHref=@0xbfffe740, aBase=0x86ed288, aReplace=1) at nsLocation.cpp:385
#15 0x403bc931 in LocationImpl::SetProperty (this=0x88a5da8, 
    aContext=0x89bd5b8, aObj=0x8808f80, aID=138084196, aVp=0xbffff228)
    at nsLocation.cpp:804
#16 0x403bd9ca in nsJSUtils::nsCallJSScriptObjectSetProperty (
    aSupports=0x88a5da8, aContext=0x89bd5b8, aObj=0x8808f80, aId=138084196, 
    aReturn=0xbffff228) at nsJSUtils.cpp:196
#17 0x403a047d in SetLocationProperty (cx=0x89bd5b8, obj=0x8808f80, 
    id=138084196, vp=0xbffff228) at nsJSLocation.cpp:286
#18 0x401f2970 in js_SetProperty (cx=0x89bd5b8, obj=0x8808f80, id=137288808, 
    vp=0xbffff228) at jsobj.c:2159
#19 0x401de029 in js_Interpret (cx=0x89bd5b8, result=0xbffff408)
    at jsinterp.c:2359
#20 0x401cfb9c in js_Execute (cx=0x89bd5b8, chain=0x874bbe8, script=0x883b390, 
    fun=0x0, down=0x0, special=0, result=0xbffff408) at jsinterp.c:857
#21 0x401a2b51 in JS_EvaluateUCScriptForPrincipals (cx=0x89bd5b8, 
    obj=0x874bbe8, principals=0x88c8570, chars=0xbffff55c, length=13, 
    filename=0x0, lineno=0, rval=0xbffff408) at jsapi.c:2754
#22 0x4039523e in nsJSContext::EvaluateString (this=0x8967e20, 
    aScript=@0xbffff544, aScopeObject=0x874bbe8, aPrincipal=0x88c856c, 
    aURL=0x0, aLineNo=0, aVersion=0x0, aRetValue=@0xbffff5dc, 
    aIsUndefined=0xbf1ffa14) at nsJSEnvironment.cpp:465
#23 0x420c0f92 in nsEvaluateStringProxy::EvaluateString (this=0x8909ad0, 
    aRetValue=0xbf1ffa18, aIsUndefined=0xbf1ffa14)
    at nsJSProtocolHandler.cpp:165
#24 0x40132da5 in XPTC_InvokeByIndex (that=0x8909ad0, methodIndex=4, 
    paramCount=2, params=0x8875a00) at xptcinvoke_unixish_x86.cpp:134
#25 0x4011bdd0 in EventHandler (self=0x88759e0) at nsProxyEvent.cpp:486
#26 0x40114dae in PL_HandleEvent (self=0x88759e0) at plevent.c:575
#27 0x40114c5c in PL_ProcessPendingEvents (self=0x8066058) at plevent.c:520
#28 0x401169e9 in nsEventQueueImpl::ProcessPendingEvents (this=0x8066030)
    at nsEventQueue.cpp:356
#29 0x40a59524 in event_processor_callback (data=0x8066030, source=9, 
    condition=GDK_INPUT_READ) at nsAppShell.cpp:158
#30 0x40a5915f in our_gdk_io_invoke (source=0x821fb78, condition=G_IO_IN, 
    data=0x821fb68) at nsAppShell.cpp:58
#31 0x40c2652a in g_io_unix_dispatch () from /usr/lib/libglib-1.2.so.0
#32 0x40c27be6 in g_main_dispatch () from /usr/lib/libglib-1.2.so.0
#33 0x40c281a1 in g_main_iterate () from /usr/lib/libglib-1.2.so.0
#34 0x40c28341 in g_main_run () from /usr/lib/libglib-1.2.so.0
#35 0x40b4f209 in gtk_main () from /usr/lib/libgtk-1.2.so.0
#36 0x40a59c1a in nsAppShell::Run (this=0x80f0a10) at nsAppShell.cpp:334
#37 0x40715aa4 in nsAppShellService::Run (this=0x8127058)
    at nsAppShellService.cpp:386
#38 0x8053b59 in main1 (argc=1, argv=0xbffffab4, nativeApp=0x0)
    at nsAppRunner.cpp:908
#39 0x805423e in main (argc=1, argv=0xbffffab4) at nsAppRunner.cpp:1094
(gdb) quit

Comment 2

[Phil Schwartau]

Notice the link under the "Search" button is a JavaScript URL:

                   JavaScript:gotoSearch();

Therefore, is this bug related to bug 41707 (JavaScript URLs don't work)?

Comment 3

[Phil Schwartau]

Also compare bug 37463 (lockup/freeze upon javascript: Window.Location = etc.)

Comment 4

[Johnny Stenback (:jst)]

This is a dup of 37463.

*** This bug has been marked as a duplicate of 37463 ***

Comment 5

[Russell East]

I've applied the patch supplied with 37463, and this fixed the problem reported 
in 43607, but not the problem reported in the current bug!

Basically 43607 went away, but all button clicks now produce the "JavaScript 
error: line 0:" message.

Comment 6

[Russell East]

I have also applied the patch indicated in 31818, since this also seemed 
appropriate, but when I tried to restart Mozilla, it just crashes with memory 
error.

The instruction at "0x..." referenced memory at "0x....". The memory could not 
be written.

Comment 7

[Johnny Stenback (:jst)]

I have hacks in my tree that fixes bugs 43652 and 37463 and I'm unable to
reproduce any of the problems mentioned here, so once those two bugs are fixed
properly this will most likely be fixed too. Setting this to Future just to get
it off my bug radar, please let me know if this is not fixed once the two
mentioned bugs are fixed...

Comment 8

[bht237]

Works for me with build 2000071215 on Win95

Comment 9

[Henrik Gemal]

Fixed in build 20001118

Comment 10

[Prashant Desale]

Verified with 2001-020608.