I am trying to add a functionality like a personal bar (similar to the one in Netscape) in my java code. After a about 3 to 6 button clicks, WebClient hangs! This is highly critical issue for the software i am writing. Please suggest a workaround or a fix. Please let me know, and I will be able to assist with anything more. I constantly notice WebClient 1.0 (with Mozilla MileStone 18) hang when loading a page, reloading, or going to a different url when the user clicks different buttons. I believe this is a timing issue, when Mozilla is trying to load a new page and is NOT done completely loading the current one. I have tried history.stop() before a navigation.loadurl(), that doesn't seem to help. To replicate the above behaviour of different button clicks, I use the following code. This replaces the navigation.loadUrl() in the EMWindow.java. String[] urlarray = {"http://www.excite.com","http://www.yahoo.com", "http://www.hotmail.com/","http://www.mp3.com", "http://www.cnn.com","http://www.mapquest.com"}; Thread t = new Thread(); t.start(); if (null != navigation) { for(int i = 0; i<6;i++){ navigation.loadURL(urlarray[i]); try{ t.sleep(1300);//You might need to play with this number }catch(InterruptedException e){ System.out.println("exception"+e); } } } t.stop(); Here is the stack trace if it helps.. "EventThread-7095200" prio=5 tid=0x6c56b0 nid=0xfff67a01 runnable [0x902f000..0x 902fda8] at org.mozilla.webclient.wrapper_native.NativeEventThread.nativeProcessE vents(Native Method) at org.mozilla.webclient.wrapper_native.NativeEventThread.run(NativeEven tThread.java:244) "AWT-Windows" prio=5 tid=0x6b7f20 nid=0xfff9f179 runnable [0x8fcf000..0x8fcfda8] at sun.awt.windows.WToolkit.eventLoop(Native Method) at sun.awt.windows.WToolkit.run(WToolkit.java:186) at java.lang.Thread.run(Thread.java:484) "SunToolkit.PostEventQueue-0" prio=5 tid=0x6b6ac0 nid=0xfff7264d waiting on moni tor [0x8f6f000..0x8f6fda8] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:420) at sun.awt.PostEventQueue.run(SunToolkit.java:496) "AWT-EventQueue-0" prio=7 tid=0x6b55d0 nid=0xfff71839 waiting on monitor [0x8f0f 000..0x8f0fda8] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:420) at java.awt.EventQueue.getNextEvent(EventQueue.java:240) at java.awt.EventDispatchThread.pumpOneEvent(EventDispatchThread.java:10 1) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) at java.awt.EventDispatchThread.run(EventDispatchThread.java:84) "Signal Dispatcher" daemon prio=10 tid=0x6a8130 nid=0xfff4b281 waiting on monito r [0..0] "Finalizer" daemon prio=9 tid=0x6a69b0 nid=0xfffa5465 waiting on monitor [0x898f 000..0x898fda8] at java.lang.Object.wait(Native Method) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:108) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:123) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:162) "Reference Handler" daemon prio=10 tid=0x6a5680 nid=0xfff72b61 waiting on monito r [0x892f000..0x892fda8] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:420) at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:110) "VM Thread" prio=5 tid=0x6a4930 nid=0xfff9d11d runnable "VM Periodic Task Thread" prio=10 tid=0x6a8950 nid=0xfffa5189 waiting on monitor -Jeet

This is bug 64332. It has been fixed in the Blackwood trunk and will be in the next release. *** This bug has been marked as a duplicate of 64332 ***

Verified DUP