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 179487 - ConcurrentModificationException
Summary: ConcurrentModificationException
Status: RESOLVED FIXED
Alias: None
Product: ide
Classification: Unclassified
Component: Exceptions Reporter (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 normal with 1 vote (vote)
Assignee: Jindrich Sedek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-14 00:32 UTC by Peter Nabbefeld
Modified: 2010-04-08 12:20 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Nabbefeld 2010-01-14 00:32:14 UTC 
There're at least two reports about it, which seem to address the same problem:
http://statistics.netbeans.org/analytics/detail.do?id=158873
http://statistics.netbeans.org/analytics/detail.do?id=163370

Seems, exception reporter does not correctly work, as also the shown component/subcomponent are not the same as in bugzilla.

I've got similar exception with a private module, which I got fixed by synchronizing my singleton instance creation. Obviously, NB tried to get my instance from 3 code fragments at about the same time. Probably this is the same here. Seems to be a multiprocessing issue.
Comment 1 Jindrich Sedek 2010-04-08 12:20:24 UTC 
both reports are already fixed and I've implemented component/subcomponent synchronization between exception reporter and bugzilla. Closing as fixed.