Actually no, I tough it was 256Mb. Thanks. It will go out of memory around 125Mb 140Mb in the task manager. It depends.
But your point just prove my problem to be even stanger: if 64 Mb shoulb be the limit where did the other 60Mb+ go? (the JVM itself never takes that much memory, not from my experience). What I did not mention in the orgininal post is that I have the same problem with an app running on 5.0.18 sam jdk, using -Xms256m -Xmx1024m, it will also run OOM, and again profiling the app did not show any leak, and a large gap between the total heap and whatever the task manger reports. My main issue here is where does the gap come from? -----Original Message----- From: Christoph Kutzinski [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:22 AM To: Tomcat Users List Subject: Re: Why is tomcat (java) so memory intensive? Philippe Deslauriers wrote: > I am using Tomcat 5.0.19 on Windows XP SP2, J2SDK 1.4.2_03. > > I have a serious memory problem with Tomcat, it just EAT memory without > explanation, until OOM error occurs. > > The Java.exe process in the windows task manager reports using between 95Mb > and 105Mb after the startup of the webapp. I do not use Xms Xmx options in > dev mode. You do know that the VM will only allocate 64 mb for heap if you don't use the Xmx option, do you? After the 64 mb are used up the vm will throw an oom error. How much memory does the taskmanager report before the oom error happens? Christoph --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
