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.
Hi: I've edited a lot of forms, opening and closing each one, and in my last opening I get the log that I send you. BTW, the rigth click on a control in the tree on the Component Inspector doesn't work. Another thing: when I change some properties like the heigth of a JTextBox, the form don't display the change until next edit or until I try to move the control or the frame that contains it.
Created attachment 3120 [details] log check last exception
after reinit the IDE, the rigth click on controls works again, but last fail was before the out of memory.
Well, this is very vague. The exception is thrown from some java parsing, but it is quite unclear why the memory ran out... We would really appreciate if you found some exact steps which done repeatedly lead into the out of memory exception. I'm reassigning to java module, if they possibly can know more. Otherwise, this will be probabl closed... > BTW, the rigth click on a control in the tree on the Component > Inspector doesn't work. Already reported, see issue 16886. > when I change some properties like the heigth of a JTextBox, the > form don't display the change until next edit or until I try to > move the control or the frame that contains it. This is quite different thing - please file it as standalone issue, and again (please) with exact reproduce steps; and also don't forget to give IDE build number... Thanks.
Hmm... I can't tell I can see anything wrong. The stacktrace shows just an ordinary parse request, as done while typing or opening the document. I am running NetBeans whole day (but don't use forms) and no OutOfMemory occurs to me :-\ Last week I've checked if there aren't dangling editor windows (referenced from somewhere even if they are closed), but for plain java the memory is wiped out from unnecessary info. Please if you find out some working pattern, that makes the bug occur (even not really deterministic), reopen the bug.
Resolved for 3.3.x or earlier, no new info since then -> closing.
Resolved for 3.4.x or earlier, no new info since then -> closing.