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 192530 - [70cat] AssertionError: removeNotify called twice or w/o addNotify()
Summary: [70cat] AssertionError: removeNotify called twice or w/o addNotify()
Status: RESOLVED DUPLICATE of bug 192801
Alias: None
Product: javame
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 7.0
Hardware: All All
: P3 normal (vote)
Assignee: Adam Sotona
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-26 14:40 UTC by marcotts
Modified: 2011-01-18 14:52 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 174385


Attachments
stacktrace (632 bytes, text/plain)
2010-11-26 14:40 UTC, marcotts
Details

Note You need to log in before you can comment on or make changes to this bug.
Description marcotts 2010-11-26 14:40:19 UTC
This bug was originally marked as duplicate of bug 170794, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 7.0 Beta (Build 201011152355)
VM: Java HotSpot(TM) Client VM, 16.2-b04, Java(TM) SE Runtime Environment, 1.6.0_19-b04
OS: Windows XP

User Comments:
marcotts: while debugging a jme project




Stacktrace: 
java.lang.AssertionError: removeNotify called twice or w/o addNotify()
   at org.netbeans.modules.mobility.project.ui.ProjectRootNodeChildren.removeNotify(ProjectRootNodeChildren.java:116)
   at org.openide.nodes.AsynchChildren.removeNotify(AsynchChildren.java:104)
   at org.openide.nodes.Children.callRemoveNotify(Children.java:573)
   at org.openide.nodes.EntrySupport$Default.finalizedChildrenArray(EntrySupport.java:910)
   at org.openide.nodes.EntrySupport$Default$ChArrRef.run(EntrySupport.java:994)
   at org.openide.util.lookup.implspi.ActiveQueue$Impl.run(ActiveQueue.java:109)
Comment 1 marcotts 2010-11-26 14:40:23 UTC
Created attachment 103377 [details]
stacktrace
Comment 2 Adam Sotona 2011-01-18 14:52:39 UTC

*** This bug has been marked as a duplicate of bug 192801 ***