Skip to main content

IE locks with new Plugin

5 replies [Last post]
tomas
Offline
Joined: 2003-06-10
Points: 0

Hi

I've been testing the new update with the Madlix.com applet using JOGL. I found that the new plug-in systems causes IE 7 to lock when draging the rigth mouse button outside of the applet window. The applet locks IE when the default "right-click" pop-window is to be displayed.

The issue can be verified with the applet at
http://www.madlix.com/Web/client/customize.do?model=694

The issue only affect IE with the new plug-in system enabled.

Cheers
// Tomas
CTO Agency9

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
kbr
Offline
Joined: 2003-06-16
Points: 0

I can reproduce the problem on Windows XP with the latest bits and both IE 6 and IE 7. It is very mysterious and whatever the problem is it appears to be quite deep in the software stack. Originally it looked like the Google Toolbar might be to blame but I removed it and the hang still occurs. When the lockup happens, iexplore.exe starts consuming a lot of CPU and java.exe stops being able to repaint. There is no Java Plug-In related code running on the browser's main thread at the time of the hang; it's doing something in mshtml.dll. On the Java side, it doesn't look like anything is obviously locked up or deadlocked, but the Java Console doesn't repaint and the Java process slowly stops being able to paint at all. I have a feeling the AWT-Windows thread may be doing something at the time of the lockup, like failing to process a focus transfer message, that causes a cross-process dependence and a storm of Windows messages resulting in the lockup. Interestingly I can't reproduce this with for example the JOGL Gears applet.

I'll look into this further and post if I file a bug about it. In the meantime it would be helpful if you could try to create a small, self-contained test case. I wonder whether the use of the Swing JFileChooser may be somehow causing problems -- I noticed there's a Swing-Shell thread running in the background in your app that I haven't seen in other apps.

tomas
Offline
Joined: 2003-06-10
Points: 0

I've tested running the JOGL Gears applet demo and I can reproduce the issue. I tested applet on 2 different winxp setups with the same problem.

kbr
Offline
Joined: 2003-06-16
Points: 0

FYI, I've filed 6686520 to track this issue. We're completely swamped right now so I can't promise when we can investigate it further, and I apologize for this. However we will track the issue and try to get to the bottom of it.

kbr
Offline
Joined: 2003-06-16
Points: 0

I was able to provoke the lockup (once) with the simplest Clock example applet from the Sun web site. I captured a native stack trace from the main thread of the IE process and added that to 6686520. We have periodic conference calls with Microsoft and I will raise the issue with them. At this point my best guess is that this is a bug in IE. I will try to capture a native stack trace of the AWT toolkit thread if I can provoke the lockup again to see if it appears to be busy when the livelock on the browser side occurs.

hdong
Offline
Joined: 2008-06-10
Points: 0

The similar issue is also talked in the thread http://forums.java.net/jive/thread.jspa?threadID=42076&tstart=0

The issue has been fixed in the latest 6u10 build