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.
Reported on behalf of J.R.Heisey and Steven Olson. I have had Win2k say that it needs to increase the virtual memory file a couple of times. I'm running with 512MB RAM. I've often had NB 3.5.1 take over 100MB and as much as 153MB of memory. With Nortan Antivirus running too my overall memory usage is always over 400MB and can go over the 512MB with a couple of IE window open. Here is some specific data. Total Netbeans Before opening NB 3.5.1 191MB used N/A NB open with two small files open 285MB used 66.5MB Opening source folder with 34 java files an 4 properties files. 71MB Tomcat running under debugger 338MB used 74.1MB NB memory usage goes up as I use it through the day repeatedly restarting Tomcat. As I said the memory usage for NB & Tomcat can hit 150 MB. I often see the disappearing script problem. I close the file and reopen it. Always works for me. JR Radim.Kubacki@Sun.COM wrote: > Steven Olson wrote: > >> Has anyone else had problems with NB 3.5.1 and JSP development? (On Windows 2000 and XP, JDK 1.4.2). >> >> I can't get NB 3.5.1 to run for more than 30-45 minutes when I'm working with JSP pages. I'll either get an Out-of-Memory error or NB will just hang. Either way, I have to kill it off and restart it in order to continue working. Also, the Editor is really unstable (for JSP development). For example, frequently large comment blocks or Java snippets get screwed up and the Editor wont allow the cursor to be positioned within the block; sometimes a scroll down and back up will help, other times it wont; in a few cases the only way I've been able to modify the code (using the Editor) is with Search/Replace. It is easier, in these cases, to just use an external editor with NB as an overblown tomcat server. >
This is really great evaluation Radime, thanks a lot for this. Filing P2 against some module is just soooo easy. What makes you feel the debugger is the problem? From the description it doesn't seem so. Please include some better evaluation of the problem. (It's very easy to file something against debugger, because debugger does almost everything else implemented in the ide - starts tomcat, compiles, executes, opens browsers, shows files in the editor, ... and the problem can be in any of these components)
I can't give you any usefull evaluation related to trunk sources when the JSP debugger is essentially broken. I can start Tomcat in debugger and it stops on breakpoint. That's all. No continue/step/run to cursor actions. I can't stop the session. Sorry. Let me know when the functionality is working.
You're right. See http://www.netbeans.org/issues/show_bug.cgi?id=42613 I filed yesterday against jpda.
Any additional info? I'm not getting any OutOfMemory problems in trunk, so Radime, if you have some info, please provide it. Thanks. If not, I'll close the bug.
not able to reproduce in recent builds
No other feedback, so verifying as worksForMe.