JDK-6556252 : Browser Freeze for Yokogawa TC03_02 Testcase becs of Memory Leak on HT m/c.
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 5.0u12
  • Priority: P3
  • Status: Closed
  • Resolution: Not an Issue
  • OS: windows
  • CPU: x86
  • Submitted: 2007-05-11
  • Updated: 2014-02-27
  • Resolved: 2009-01-21
Related Reports
Relates :  
JDK-6556254 - Browser Freezes while running Yokogawa Reliability TC04_01 (ArcDemo) after 12 hours.
Relates :  
JDK-6540130 - Out of Memory Error occurs when open and close applet in IE7 many times
Relates :  
JDK-6505072 - Memmory,Handles and GDI Objects leaks while loading ArcTest Demo.
Description
Yokogawa TC03_02 Browser Freezes after running aroung 13 hours.  There is a major Memory Leak and GDI Objects  leak observed. 
M/c  Windows XP - Hyper Threaded m/c  ( This passes on non HT m/c)

Time Recorded                   16:02:01  .. 05:46:15      
Thread Count                   [27 .. 34]
Handle Count Range             [817 .. 1565]
Private Bytes                  [34,508,800 .. 68,177,920]
Working Set                    [42,487,808 .. 73,805,824] 
GDI                            [277 .. 9996] 

Following Exceptions are recorded in trace file just beore the freeze.
Exception in thread "frame-creator" java.lang.InternalError: couldn't create component peer
        at sun.awt.windows.WComponentPeer.checkCreation(Unknown Source)
        at sun.awt.windows.WComponentPeer.<init>(Unknown Source)
        at sun.awt.windows.WCanvasPeer.<init>(Unknown Source)
        at sun.awt.windows.WPanelPeer.<init>(Unknown Source)
        at sun.awt.windows.WWindowPeer.<init>(Unknown Source)
        at sun.awt.windows.WFramePeer.<init>(Unknown Source)
        at sun.awt.windows.WEmbeddedFramePeer.<init>(Unknown Source)
        at sun.awt.windows.WToolkit.createEmbeddedFrame(Unknown Source)
        at sun.awt.windows.WEmbeddedFrame.<init>(Unknown Source)
        at sun.awt.windows.WEmbeddedFrame.<init>(Unknown Source)
        at sun.plugin.viewer.frame.IExplorerEmbeddedFrame.<init>(Unknown Source)
        at sun.plugin.viewer.IExplorerPluginObject.createFrame(Unknown Source)
        at sun.plugin.viewer.IExplorerPluginObject$1.run(Unknown Source)
java.lang.NullPointerException
        at sun.plugin.viewer.IExplorerPluginObject$2.run(Unknown Source)
Exception in thread "frame-creator" java.lang.InternalError: couldn't create component peer
        at sun.awt.windows.WComponentPeer.checkCreation(Unknown Source)
        at sun.awt.windows.WComponentPeer.<init>(Unknown Source)
        at sun.awt.windows.WCanvasPeer.<init>(Unknown Source)
        at sun.awt.windows.WPanelPeer.<init>(Unknown Source)
        at sun.awt.windows.WWindowPeer.<init>(Unknown Source)
        at sun.awt.windows.WFramePeer.<init>(Unknown Source)
        at sun.awt.windows.WEmbeddedFramePeer.<init>(Unknown Source)
        at sun.awt.windows.WToolkit.createEmbeddedFrame(Unknown Source)
        at sun.awt.windows.WEmbeddedFrame.<init>(Unknown Source)
        at sun.awt.windows.WEmbeddedFrame.<init>(Unknown Source)
        at sun.plugin.viewer.frame.IExplorerEmbeddedFrame.<init>(Unknown Source)
        at sun.plugin.viewer.IExplorerPluginObject.createFrame(Unknown Source)
        at sun.plugin.viewer.IExplorerPluginObject$1.run(Unknown Source)
java.lang.NullPointerException
        at sun.plugin.viewer.IExplorerPluginObject$2.run(Unknown Source)
Exception in thread "frame-creator" java.lang.OutOfMemoryError: too many window handles
        at sun.awt.windows.WToolkit.eventLoop(Native Method)
        at sun.awt.windows.WToolkit.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Exception in thread "frame-creator" java.lang.OutOfMemoryError: too many window handles
        at sun.awt.windows.WToolkit.eventLoop(Native Method)
        at sun.awt.windows.WToolkit.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Exception in thread "frame-creator" java.lang.OutOfMemoryError: too many window handles
        at sun.awt.windows.WToolkit.eventLoop(Native Method)
        at sun.awt.windows.WToolkit.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)


Applet Location: 
http://sqindia.india.sun.com/~rn195728/TC03_02/TC03-02_Top.html  

How to reproduce:

How to reproduce. ( You need to install MKS on this system or rewrite the scripts to bat)
1. Unzip the the attached yokogawa.zip file to a dir say C:\temp
2. cd C:\temp\yokogawa
3. set the TEST_JRE_HOME env. variable
	e.g. set TEST_JRE_HOME=c:\Program Files\Java\jre1.5.0_12 ( with out quates)
4. sh tc3_002.sh 
This test case will launch an applet and will run for  24 hours. You can custmize the duration to run by changing "-timeout" value in 
yokogawa.sh script. 

Output directory also can be customized by changing "-outputdir" 
TestCase URL can be hosted on a local system and customize it by changing the yokogawa.sh script.
Trace and log file will be located under outputdir by defalut (from where you are running)
iexplore.csv will contain the handle count, thread count, privite bytes, working set, %Processor Time and GDI Objects counter values at various points for iexplore.exe process.
Comments
EVALUATION Handle leak is IE7 related. Disabling Phishing filter in IE7 should fix the handle leak. The following are related patches for IE7 KB955478 Phishing Filter situation with Internet Explorer 7.0 KB956625 Microsoft Text Services situation on Windows XP and Windows Server 2003.
21-01-2009
EVALUATION There's no GDI objects leak nor freeze observed with jre 6u2 promoted build. Marking this bug as mustang-na. However, there're handles and memory leaks need to be investigated in the context of jre 6update. See evaluation of 6540130 for details.
21-05-2007