Tomcat debugging memory black hole in 4.5

Has anyone else experienced this? I am using Tomcat 5.0.27. Everytime I start a debug session it creates one cmd.exe and one java.exe service. After I stop the session the services keeps running. Eventually the system runs out of memory.
Unfortunately I am stuck using 4.03 until this is fixed.

9 comments
Comment actions Permalink

Yes, read the forum, it's been reported many times. There is no current
solution, however the advice from JB is usually to download the YouKit EAP
and take a snapshot and send it to them for review.

I don't know if anyone has done that yet. I haven't because I'm on a Mac
and I don't have this problem.

R


On 8/12/04 11:47 AM, in article
15139513.1092325624621.JavaMail.itn@is.intellij.net, "bobmanc"
<no_mail@jetbrains.com> wrote:

Has anyone else experienced this? I am using Tomcat 5.0.27. Everytime I start
a debug session it creates one cmd.exe and one java.exe service. After I stop
the session the services keeps running. Eventually the system runs out of
memory.
Unfortunately I am stuck using 4.03 until this is fixed.


0
Comment actions Permalink

I have read the forum butI am suprised more people are not complaining about this. I thought I would bring it up again. Using Yourkit wouldn't help since the leak is not within IDEA.

0
Comment actions Permalink

Then if it's not within idea, why would people complain here???

R


On 8/15/04 3:32 PM, in article
13283770.1092598336682.JavaMail.itn@is.intellij.net, "bobmanc"
<no_mail@jetbrains.com> wrote:

I have read the forum butI am suprised more people are not complaining about
this. I thought I would bring it up again. Using Yourkit wouldn't help since
the leak is not within IDEA.


0
Comment actions Permalink

There is no memory leak in IDEA but IDEA is not shutting down the Tomcat service when you close your debug session from IDEA. Hence you get a new Tomcat service running every time you start and stop a debug session which leads to a lot of memory being used.

0
Comment actions Permalink

Well, this all seems like a mute point as it looks like 4.5.1RC1 fixes the bug!

0
Comment actions Permalink

bobmanc wrote:

Well, this all seems like a mute point as it looks like 4.5.1RC1 fixes the bug!


You mean a "moot" point.

/Kreiger

0
Comment actions Permalink

I spoke too soon. It looks like this is NOT fixed in v4.5.1.

0
Comment actions Permalink

I tried adding this bug to the buglist and it doesn't ever get posted so I'll keep harping on it here. It's still not fixed and I can't use 4.5 at all.

0

Please sign in to leave a comment.