Thanks for the replies. The -client worked. Dropped memory usage down
to ~70Mb. Still little high, and the Xms options don't seem to make any
difference when used.
Will try the memory profiler to see what it shows.
On 7/26/10 10:04 PM, David Bullock wrote:
On 27 July 2010 02:16, CJ Keist <[email protected]
<mailto:[email protected]>> wrote:
But when I looking at the kiosk sessions this little java app is
chewing up 571MB of memory!
I'd have expected it to be below 12MB for a trivial Swing application.
It's possible to inadvertently hang on to object references in Java
and cause a memory leak. I'd ask your coder to use NetBeans' memory
profiler and see if there are more objects surviving garbage
collection than they expect.
regards,
David.
(SCJP - although I guess that's now an OCJP).
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
--
C. J. Keist Email: [email protected]
UNIX/Network Manager Phone: 970-491-0630
Engineering Network Services Fax: 970-491-5569
College of Engineering, CSU
Ft. Collins, CO 80523-1301
All I want is a chance to prove 'Money can't buy happiness'
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
