This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 34264

Summary:	cpu tight loop / hang when printing JUnit help.
Product:	platform	Reporter:	schwarcz <schwarcz>
Component:	-- Other --	Assignee:	issues@platform <issues>
Status:	CLOSED WONTFIX
Severity:	blocker	CC:	jchalupa, mmirilovic, pzajac, ttran
Priority:	P1	Keywords:	JDK_SPECIFIC
Version:	3.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:
Attachments:	ide log ide log from second system thread dump thread dump with jdk 1.4.1_03 jdk1.2.2 threads dump

Description schwarcz 2003-06-10 04:39:53 UTC

Open the Junit help (Help | Help Sets | Junit Module Help 
and then seelct a page such as JUnit Module Settings.  
Attempt to Print the page.  The print dialog comes up.  
Once the dialog is completed, cpu utilization goes to 
100%.  Once in this state there is no way to continue 
without killing the two processes (NetBeans and JUnit 
Module Help) which results in the loss of any file 
modifications which had not been saved to disk.


I originally discovered this bug with 3.5RC3, then 
upgraded to the final release of 3.5 and duplicated it.  I 
have been able to replicate it at will on two different 
computers, two different operating systems (Win XP Pro and 
Win 2K).  The problem does not seem to depend upon the 
target printers (HP LJ 3100 and HP LJ 5MP).

I have been able to print other random help pages without 
problem so feel that there is something interesting about 
the JUnit module help.

Comment 1 schwarcz 2003-06-10 04:40:47 UTC

Created attachment 10628 [details]
ide log

Comment 2 schwarcz 2003-06-10 04:43:20 UTC

Created attachment 10629 [details]
ide log from second system

Comment 3 pzajac 2003-06-10 08:33:20 UTC

probably problem in JDK. Can you add threads dump (CTRL + BRK on
console)?

Comment 4 schwarcz 2003-06-10 17:12:27 UTC

Created attachment 10640 [details]
thread dump

Comment 5 pzajac 2003-06-12 13:38:36 UTC

Carl thanks to your report. 
This is a real problem with jdk,  awt  thread is waiting at :
at java.lang.Double.toString(Double.java:135)

can you try use jdk 1.4.1_03 ?

Comment 6 schwarcz 2003-06-12 16:37:51 UTC

Created attachment 10673 [details]
thread dump with jdk 1.4.1_03

Comment 7 schwarcz 2003-06-12 16:38:38 UTC

Yes, the problem is easily reproducable under jdk 
1.4.1_03.  (See thread dump just attached).

Comment 8 pzajac 2003-06-13 07:31:57 UTC

this is serious problem. I can reproduce it on Win2k an jdk1.2.2beta
too.  At least it can be added to release notes.

Comment 9 pzajac 2003-06-13 07:34:37 UTC

Created attachment 10678 [details]
jdk1.2.2 threads dump

Comment 10 Marian Mirilovic 2003-06-13 13:20:55 UTC

Reproducible on Sol8/jdk1.4.1_02

Comment 11 Marian Mirilovic 2003-06-18 10:06:39 UTC

It's known Javahelp issue, see
http://developer.java.sun.com/developer/bugParade/bugs/4768427.html

Comment 12 Marian Mirilovic 2003-07-28 16:49:37 UTC

closing.