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 22500 - Another CME (ConcurrentModificationException)
Summary: Another CME (ConcurrentModificationException)
Status: CLOSED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcscore (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords: THREAD
Depends on:
Blocks:
 
Reported: 2002-04-16 15:45 UTC by dmladek
Modified: 2003-07-01 12:57 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
CME stacktrace (2.66 KB, text/plain)
2002-04-17 09:44 UTC, dmladek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description dmladek 2002-04-16 15:45:51 UTC
Product Version       = NetBeans IDE Development
Version (Build 200204150100)
  IDE Versioning        = IDE/1 spec=2.11
impl=200204150100
  Operating System      = Linux version 2.4.10
running on i386
  Java; VM; Vendor      = 1.4.1-beta; Java
HotSpot(TM) Client VM 1.4.1-beta-b08; Sun
Microsystems Inc.
  Java Home             =
/usr/java/j2sdk1.4/sun/jdk1.4.1/jre  System
Locale; Encod. = cs_CZ; ISO-8859-2
======================================================================

I don't have any ide how this CME appeared:-(
I was just only editing some file....
I dind't do relatively previously cvs action.
I have mounted one GCVS and a few JavaCVS FSs.

Filling this as a bug just only my hope you'll be
able to recognize 
problem from the stacktrace of
ConcurrentModificationException
Comment 1 Martin Entlicher 2002-04-16 16:43:50 UTC
Can you attach the stacktrace??
Comment 2 dmladek 2002-04-17 09:44:56 UTC
Created attachment 5439 [details]
CME stacktrace
Comment 3 dmladek 2002-04-17 09:47:58 UTC
I'm sorry...unluckyly an attaching failed and I didn't notice that:-(
Comment 4 Martin Entlicher 2002-04-17 10:35:24 UTC
Reassigning...
Comment 5 Martin Entlicher 2002-04-17 10:36:06 UTC
The problem found, starting to work on it...
Comment 6 Martin Entlicher 2002-04-17 10:44:37 UTC
Problem fixed in dev build Apr 18.
This bug is hardly reproducible unless you write a special testcase.
Reopen if it ever re-appears.
Comment 7 dmladek 2002-05-10 14:35:15 UTC
Using latest dev NB3.4 build and exercising with them didn't lead to
reproduction of the CME.
So I believe it's realy fixed (as you wrote 'cause I don't have
spec.testcase and no idea how to test it).
Comment 8 Quality Engineering 2003-07-01 12:57:19 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.