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.
Adding a plugin to my Grails project via UI. This fire FS FileUtil.refreshFor in event thread and slowness reporter is trying to report it. So far so good. However such attempt leads to OOME quite often and IDE is unusable since then (only kill -9 works). Attaching threaddumps, messages.log. I can provide heapdump as well (it is 65MB when compressed). I remember I saw same behavior in another case.
Created attachment 87586 [details] 1st threaddump
Created attachment 87587 [details] 2nd threaddump
Created attachment 87588 [details] ide log
Why is this issue assigned to logger? There is now logger line in threaddump neither ide log. All info is pointing me to a problem in groovy or Parsing infrastructure that fails because of lack of memory. Could you place heapdump somewhere (for example to beetle) so I could download it? It's possible that profiler self sampling takes some memory, but it won't run during FCS builds, so we should more likely optimize groovy than logger.
Feel free to reassign to proper component. Is there any for slowness detector? I though this is the right one. Neither groovy nor parsing is cause of this (without slowness detector it works quite fine). Slowness detector is imo the indirect cause of OOME.
I had problems with reading heapdump because of issue #172256, but I tried to lower memory consumption while invoking notification fixed. 4166d888a9d0
Integrated into 'main-golden', will be available in build *200909181401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/4166d888a9d0 User: Jindrich Sedek <jsedek@netbeans.org> Log: issue #172150 - IDE completely frozen by slowness reporter