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 32582 - Printing from online help uses 100% cpu
Summary: Printing from online help uses 100% cpu
Status: VERIFIED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Help System (show other bugs)
Version: 3.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: _ tboudreau
URL:
Keywords: JDK_SPECIFIC
Depends on:
Blocks:
 
Reported: 2003-04-02 23:31 UTC by Chris Kutler
Modified: 2008-12-22 19:02 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Kutler 2003-04-02 23:31:13 UTC
Mostly (but not always) when I try to print a
topic from the online help (JavaHelp), the
runide.exe starts consuming cpu and memory and I
never get the print out. I have to kill the
runide.exe app instead.

About 5 minutes ago, I tried the print and the
task manager shows that runide.exe is using 99%
cpu, no other processes are using cpu.

When I first look, the Memour usage was 70,000.
Now it is up to 138,54. I am not using the PC and
haven't since I started monitoring this print
request.

I restarted and printed from the source editor ok,
printed one help topic ok, and then tried another
topic and the above happened.
Build o30401. Java 1.4.1_01
Comment 1 pzajac 2003-04-03 09:12:10 UTC
Printing from help on linux works correctly. It is probably
JDK/Windows specific. 
Comment 2 _ tboudreau 2003-04-03 11:13:45 UTC
How big was the topic you were trying to print?  AFAIK, printing
in JDK 1.2 and up creates a gargantuan bitmap and sends it to the
printer.  So printing something small might not be a problem, but
printing something enormous can get pretty huge.  That is a Java
issue, not so much a NetBeans issue - I don't know if there have
been improvements in more recent JDKs (I last tried printing from
the IDE in 1999 on an early 1.3 - the experience was pretty 
aversion-producing).

Also could be an issue in JavaHelp itself (also a JDK bug), since
the printing support is implemented there.  Not sure there's much
we can do about it, but will try to investigate it at some point.
Comment 3 Chris Kutler 2003-04-03 15:14:55 UTC
The topics are very small.  I have not seen any pattern that
determines when I will be successful. An example of a topic that won't
print is in the JSP/Servlet help set titled  Upgrading to JSP 1.2 and
Servlet 2.3 Specifications.

In my experiments to try and narrow down the cause, I have seen a
situation where I print a topic successfully once, try again and it
won't print.

Also, I did not have this problem last week, so it may have been
introduced by a change. Or it may be a problem specific to this
section of the help set.
Comment 4 bwalle 2003-07-29 08:02:15 UTC
Same problem here.

$ java -version
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)

$ uname -a
Linux hugo 2.4.21 #1 Don Jul 24 22:28:38 CEST 2003 i686 unknown
Comment 5 _ tboudreau 2003-11-15 16:37:47 UTC
Closing this as fixed - there was a bug in 1.1.3 that could cause a
lot of looping if a page break occured in just the right spot
(basically JavaHelp endlessly trying to format the same page).  The
author of JavaHelp has informed me this is fixed in JavaHelp 2.0,
which the trunk builds use.

If you experience the problem with a current trunk build, please reopen.
Comment 6 Marian Mirilovic 2004-06-30 11:02:29 UTC
verified in [nb_dev](200406291800)