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 21267 - new JSP page causes memory to continually increase and causes Out of Memory Exception
Summary: new JSP page causes memory to continually increase and causes Out of Memory E...
Status: CLOSED DUPLICATE of bug 20490
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Infrastructure (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P1 blocker (vote)
Assignee: issues@projects
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2002-03-06 17:39 UTC by carlson
Modified: 2003-07-01 14:17 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Full Thread dump with description after adding jsp page (22.28 KB, text/plain)
2002-03-12 16:44 UTC, carlson
Details
Full thread dumps adding second jsp page with description and time frames (50.83 KB, text/plain)
2002-03-12 16:47 UTC, carlson
Details
Out of memory exception (844 bytes, text/plain)
2002-03-12 16:50 UTC, carlson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description carlson 2002-03-06 17:39:27 UTC
Hi,
When I create a new JSP Page the memory continually increases after 
that point. Also the explorer filesystems window does not refresh with the 
newly created file. Also any new nodes I try to open after I create a new 
JSP page also do not show any contents. (see description below).

Memory usage description
I had the memory usage toolbar open, and the memory was continually 
consumed (started at 40MB then went to 80+ MB (then I got an out of 
memory error). I did nothing after I created the JSP page except put the 
mouse over the memory meter to get the value.
After I got the out of memory error, the memory went back down to 40MB, 
but then started to climb again (about 1MB every 10 to 20 seconds), until I 
get another Out of Memory error.

I clicked on the gc toolbar item and that would bring down the memory 
about 2MB, but it would still just keep climbing.

Here is the exception
Wed Mar 06 09:34:16 PST 2002: java.lang.OutOfMemoryError: <no 
message>

java.io.IOException

        at 
org.openide.loaders.DataLoader.findDataObject(DataLoader.java:230)

        at 
org.openide.loaders.DataLoaderPool.findDataObject(DataLoaderPool.jav
a:363)

        at org.openide.loaders.FolderList.createBoth(FolderList.java:576)

        at org.openide.loaders.FolderList.getObjects(FolderList.java:395)

        at org.openide.loaders.FolderList.access$200(FolderList.java:43)

        at org.openide.loaders.FolderList$ListTask.run(FolderList.java:743)

        at org.openide.util.Task.run(Task.java:152)

[catch] at 
org.openide.util.RequestProcessor$ProcessorThread.run(RequestProce
ssor.java:622)

Wed Mar 06 09:34:16 PST 2002: java.lang.OutOfMemoryError: <no 
message>

java.lang.OutOfMemoryError

[catch] <<no stack trace available>>



---------------

JSP Page Creation.
I went to a folder in the Filesystems and right clicked then selected new --
> JSP Page.


Let me know if you want more debugging

I am using NB 3.3 (build 20011202331) on Windows 2000 with 512 MB 
RAM on a P4 1.5 GHz.

Thanks

--Peter
Comment 1 _ ttran 2002-03-06 19:52:14 UTC
added PERFORMANCE keyword
Comment 2 _ ttran 2002-03-06 20:15:35 UTC
Peter, is the bug reproducible?  Does it happen immediately after the
start of the IDE or after you has been doing other activities?  (I am
trying to guess if it's indeed related to JSP or an after-the-fact
side effect of other actions)
Comment 3 _ ttran 2002-03-07 17:15:14 UTC
Petre, please start investigate
Comment 4 Petr Nejedly 2002-03-07 18:05:47 UTC
If it is reproducible, I'll try to investigate it myself.
Please try to make some thread dumps during the time the memory
usage grows and post them here (as attachement).

Do you have any nonstandard module installed? (there was similar
problem reported in association with InnerTesters, see issue 21056)

Comment 5 Petr Nejedly 2002-03-11 15:44:54 UTC
I cannot reproduce it here. Did it happened just once or is it
reproducible on your side? We need more feedback on this or I'll
have to close the issue.
Comment 6 carlson 2002-03-12 16:44:54 UTC
Created attachment 5035 [details]
Full Thread dump with description after adding jsp page
Comment 7 carlson 2002-03-12 16:47:49 UTC
Created attachment 5036 [details]
Full thread dumps adding second jsp page with description and time frames
Comment 8 carlson 2002-03-12 16:49:16 UTC
I am able to reproduce this with a reinstall of 3.3.1.

I am attaching 3 files.
1) Full Dump after adding first jsp with description
2) Full Dump after adding second jsp with description
3) Out of memory error
 
The memory growth is a little slower now (about 1 -2 MB/min)

Please let me know what else you need.
Comment 9 carlson 2002-03-12 16:50:08 UTC
Created attachment 5037 [details]
Out of memory exception
Comment 10 Petr Nejedly 2002-03-12 23:23:39 UTC
It seems that there is some problem in projects module causing scan
of some deep directory structure.
Don't you have a lot of .xml files in some of your mounted
filesystems? Most of the time
is spent recognizing some xml files and they have to be opened to be
recognized.
To the OOME: If you have a lot of the files in the filesystems and the
projects module
cause their recognition and hold them referenced, memory can vanish.

I have to investigate what does the projects module do wrong. You can
try to disable
it (if you don't depend on its functionality) and check whether it is
better.

Also, could you describe your mounted filesystems (e.g. there is one
with 1000 .java files
and the other with 200 xml files in such and such hierarchy)?
Comment 11 carlson 2002-03-13 15:49:35 UTC
Hi,
Your right that there are lots of xml files.   They are data files that 
contain documents. They are not part of the programming 
environment, just in the same hierarchy.

After removing the thousands of xml files, It seems to work great.

How can I disable the recognition?

Thanks for you help

Is there anything else you want me to investigate?

--Peter
Comment 12 Petr Nejedly 2002-03-14 10:47:04 UTC
That explains a lot.
I'm reassigning it to projects to let them investigate their part.
I have some more questions, which may help them too:
What filesystems did you have mounted?
Were the xmls in the same filesystem as the new JSP?
Where in the filesystem were the xml files (relative path)?
Where in the filesystem was the new JSP created (relative path)?

As a workaround, you can disable the projects module if you can
live without it. Disabling ant module can also help.
Comment 13 Vitezslav Stejskal 2002-03-16 00:47:41 UTC
this was already fixed in main trunk

marking 3.3.2_CANDIDATE as it is severe performance problem and the 
fix is trivial

*** This issue has been marked as a duplicate of 20490 ***
Comment 14 Vitezslav Stejskal 2002-03-27 15:43:44 UTC
INF=6163, integrated from main trunk to orion_fcs branch
Comment 15 Milan Kubec 2002-04-02 12:57:12 UTC
Verified duplicate; Verified in ffj-020401.
Comment 16 Quality Engineering 2003-07-01 14:17:06 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.