Dear members,
A while back, I posted a plea for help with a Java problem which was crashing TOPSPIN 1.3. (I have appended this message with the original post). The cause of this problem was the unfavorable interaction between the JAVA used by TOPSPIN 1.3 and the screen saver WINDOWS XP was using (specifically, the WINDOWS 3D text screen saver). When this screen saver is turned off (or when a different screen saver is used), the problem disappears.
Thank you very much to Mike Engelhardt and Robin Stein of Bruker for spending so much of his time on this.
Cheers,
Glenn
Dr. Glenn A. Facey
NMR Facility Manager,
Department of Chemistry, University of Ottawa
10 Marie Curie, Ottawa, Ontario, K1N 6N5
CANADA
ph. (613) 562-5800 ext 6077
fax. (613) 562-5170
email. gafacey_at_uottawa.ca<mailto:gafacey_at_uottawa.ca>
web. www.science.uottawa.ca/nmr<
http://www.science.uottawa.ca/nmr>
www.u-of-o-nmr-facility.blogspot.com<
http://www.u-of-o-nmr-facility.blogspot.com>
________Original Post______________
Dear members,
I am frustrated with a java problem I am having on a WINDOWS XP Hewlett Packard PC running a spectrometer under TOPSPIN 1.3 and I am seeking your help. The problem is as follows:
The problem:
1. After a day or so of operation the computer comes to an absolute crawl and TOPSPIN must be exited (if possible). After exiting TOPSPIN the computer runs fine.
2. When the computer is running VERY slowly a process called "javaw.exe" is consuming a HUGE amount of memory.
3. When TOPSPIN is exited after running slowly, a VERY LARGE file of the type "javaw_pid###.hprof" is created in the TOPSPIN directory, where "###" is the pid number of the java virtual machine (JVM) process which starts when TOPSPIN 1.3 is started. If allowed to accumulate, these files will fill the disk in a matter of weeks.
What I have tried to solve it:
1. I upgraded TOPSPIN 1.3 patch level 8 to patch level 10. The same problem exists but the offending process consuming large amounts of memory is now "java.exe" and not "javaw.exe". The large files being created are now "java_pid####.hprof" and not "javaw_pid###.hprof"
Has anyone had similar problems? Does anyone have any suggestions for a fix?
Received on Wed Jan 18 2012 - 08:19:45 MST