-
Bug
-
Resolution: Fixed
-
P4
-
1.1, 1.3.0
-
ladybird
-
x86
-
windows_nt
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2034373 | 1.4.0 | Scott Violet | P4 | Resolved | Fixed | beta |
Name: skT45625 Date: 05/24/2000
D:\Data\InterLinx2.0\Release\help\JavaHelpFiles>java -version
java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-C)
Java HotSpot(TM) Client VM (build 1.3.0-C, mixed mode)
Launching the help viewer causes excessive CPU and memory usage especially when
an HTML file that references many graphic objects (gifs) is opened.
The CPU usage and memory continues to be an issue if the help viewer is used for
browsing purposes after its initial launch. After 20 minutes or so of use the
java VM is running at 64Mb and large HTML files can take 30 seconds to be fully
retrieved and displayed.
The help files being used were generated by the "RoboHelp" product and are held
as a jar file. These help files were previously used successfully in WinHelp
format by launching the Microsoft WinHelp viewer. We now want to move to a pure
Java Help solution since we are issuing our Application for Sun Solaris. The
performance of the JavaHelp viewer is unacceptable in our move to Solaris.
Running the JavaHelp demo programs also gives memory problems, but they are less
CPU intensive probably because they are more text based.
Extracting my helpfiles from the jar and launching the HTML files in any other
Browser (Netscape, IE or HotJava) cause near instantaneous display and no
perceived CPU or memory problems. However using freestanding files and the
JavaHelp viewer still suffer the CPU and memory performance problems.
The performance problems can clearly be seen in the Windows NT task manager.
My system is Windows NT 4.0 SP5, running on a Pentium II 450 MHz with 256 MB
RAM.
(Review ID: 104977)
======================================================================
- backported by
-
JDK-2034373 JavaHelp viewer (JEditorPane) suffers CPU thrashing and excessive memory usage.
-
- Resolved
-