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.
got it with next steps - register new mysql database - start it - create new db with grand all to root::1 - go to connection url node - expand this url, - expand newly created db node(default one/bold one) see tables and views node and 'wait..' node on 3rd inner node place ide freeze headdump is automatically created
see http://deadlock.netbeans.org/hudson/job/upload/100/parameters/? should be at least P2 in my opinion
The issue could be related to bug 221817. Can you please verify it? (The fix is simple, see http://hg.netbeans.org/core-main/rev/0c9de3ddbd5c).
It's hard to say, I'm trying to evaluate the dump but my system is too slow right now. On top there are a lot of StackTraceElemenst so OOM may be exception reporter related but on other side it may mean some stackoverlow exception in db as latest actions was in Services/DB
Created attachment 127643 [details] message.log but I see nothing db related here
there is wrong link to head dump above, proper one should be http://deadlock.netbeans.org/hudson/job/upload/101/parameters/?
*** Bug 221980 has been marked as a duplicate of this bug. ***
> On top there are a lot of StackTraceElemenst so OOM may be exception reporter > related but on other side it may mean some stackoverlow exception in db as > latest actions was in Services/DB One of symptoms of bug 221817 is StackOverflow, so it might be related. > proper one should be > http://deadlock.netbeans.org/hudson/job/upload/101/parameters/? Thank you, I'll try to analyze it too (after I download it).
if it's the case oom may be need to be filed as separate issue for exception reporter in case of stackoverflow.
as stacktrace element have nothing common with reporter and is part of exception, I may be wrong above. Hard to say yet if it's related to fixed issue, I see stacktrace elements contain Nodes and number of related methods and don't see binding to db yet, it's better to know relative area to knwo what to look for.
(In reply to comment #9) > as stacktrace element have nothing common with reporter and is part of > exception, I may be wrong above. Hard to say yet if it's related to fixed > issue, I see stacktrace elements contain Nodes and number of related methods > and don't see binding to db yet, it's better to know relative area to knwo what > to look for. I'm not sure, but I think it is related. Several strange problems were reported against db module since Friday. The problem in the fixed issue is that a node was assigned to two parents, which makes the IDE very unstable (I don't know why it started to cause the error, as it worked fine before). The biggest object in the heapdump is an IllegalStateException. Maybe the memory was consumed before the exception could have been logged: Class Name Retained Size ---------- ------------- java.lang.IllegalStateException#2503 128 273 346
just got next output : Caused: java.lang.IllegalStateException: Cannot initialize 0th child of node org.netbeans.modules.db.explorer.node.SchemaNode[name=lab6][Name=lab6, displayName= lab6]; it already belongs to node org.netbeans.modules.db.explorer.node.CatalogNode[name=lab6][Name=lab6, displayName=lab6] (did you forgot to use cloneNode?) Children of new node: null Children of old node: null Caused: java.lang.IllegalStateException: Cannot initialize 0th child of node org.netbeans.modules.db.explorer.node.SchemaNode[name=lab6][Name=lab6, displayName= lab6]; it already belongs to node org.netbeans.modules.db.explorer.node.CatalogNode[name=lab6][Name=lab6, displayName=lab6] (did you forgot to use cloneNode?) Children of new node: null Children of old node: null Caused: java.lang.IllegalStateException: Cannot initialize 0th child of node org.netbeans.modules.db.explorer.node.SchemaNode[name=lab6][Name=lab6, displayName= lab6]; it already belongs to node org.netbeans.modules.db.explorer.node.CatalogNode[name=lab6][Name=lab6, displayName=lab6] (did you forgot to use cloneNode?) Children of new node: null Children of old node: null and finally OOM, on the same action, will try after fix propagation.
it's not in our repository yet, so can't verify yet, may be closed as duplicate anyway, will reopen if will be able to reproduce.
(In reply to comment #12) > it's not in our repository yet, so can't verify yet, may be closed as duplicate > anyway, will reopen if will be able to reproduce. OK, closing as duplicate. Thank you very much. *** This bug has been marked as a duplicate of bug 221817 ***