This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 41427 - IDE becomes sluggish and hangs
Summary: IDE becomes sluggish and hangs
Status: RESOLVED DUPLICATE of bug 40233
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 3.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Pavel Buzek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-26 20:57 UTC by Ana.von Klopp
Modified: 2004-08-13 12:11 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Thread dump (11.04 KB, text/plain)
2004-03-26 21:00 UTC, Ana.von Klopp
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ana.von Klopp 2004-03-26 20:57:54 UTC
I had worked on code for an hour or so, and then 
minimized it for several hours. Initially when I 
brought it up the UI didn't do anything at all, it 
eventually recovers and returns to normal 
responsiveness but this took about five minutes.

I have observed this a couple of times now, 
attaching a thread dump this time.
Comment 1 Ana.von Klopp 2004-03-26 21:00:06 UTC
Created attachment 14179 [details]
Thread dump
Comment 2 Pavel Buzek 2004-03-29 18:40:22 UTC
Moving to tomcat since it looks like tomcat related issue.

Looking at the thread dump I realize I do not understand one thing:
how can there be tomcat threads mixed with IDE threads? I think I am
missing something, I thought nothing from tomcat should be in IDE VM.

Also, it seems there are 3 threads in CompyMaker.read which looks
strange. Adding Petr and Martin to CC. 
Thanks for advice.
Comment 3 Martin Grebac 2004-03-30 08:23:25 UTC
I'm not sure about this, too. It can be parser that we use internally,
or httpserver?
The copymakers ar for output/error stream handling.
Comment 4 Petr Jiricka 2004-04-02 09:50:24 UTC
Three copymakers is correct: input, output, error streams.

The Tomcat thread is the internal HTTP server.

I sometimes see this behavior too, and I think it could be because
Windows swaps out the application, and then loads it back to the
memory. Loading it back takes a long time. That's just a hypothesis,
though.

Comment 5 Pavel Buzek 2004-04-05 18:51:14 UTC
Not a showstopper for 3.6.
Comment 6 _ rkubacki 2004-04-15 09:25:52 UTC
This is a known problem on a Win platform. I am marking this as a dup
of existing bug

*** This issue has been marked as a duplicate of 40233 ***