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 23990 - IllegalArgExc when opening imported project
Summary: IllegalArgExc when opening imported project
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Peter Zavadsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-24 13:03 UTC by Milan Kubec
Modified: 2008-12-23 09:35 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
exception stack trace (3.33 KB, text/plain)
2002-05-24 13:03 UTC, Milan Kubec
Details
exc stack trace with Comp. Inspector (932 bytes, text/plain)
2002-06-03 12:10 UTC, Milan Kubec
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Milan Kubec 2002-05-24 13:03:05 UTC
I imported project from NetBeans 321 and after
opening it I got IllegalArgumentException and no
windows were restored. The project is saved on
Editing WS and 4 different files are opened in
Editor. Exc is attached.
Comment 1 Milan Kubec 2002-05-24 13:03:53 UTC
Created attachment 5948 [details]
exception stack trace
Comment 2 Milan Kubec 2002-05-24 13:13:04 UTC
Increasing priority since after this exception any other project
cannot be opened.
Comment 3 Milan Kubec 2002-05-24 13:23:03 UTC
Descreasing back to P3, because the problem was caused by another
exception thrown too.
Comment 4 Vitezslav Stejskal 2002-05-24 13:51:35 UTC
exception is thrown from core/winsys
Comment 5 Vitezslav Stejskal 2002-05-24 13:52:07 UTC
x
Comment 6 Peter Zavadsky 2002-05-28 08:53:12 UTC
The problem is in DefaultConainerImpl the field topComps is not
synchronized enough, and accessing the field from threads (note from
stack trace it is accessed not from AWT ) leads to race condition,
what causes this bug.

Will try to synchronize the tomComps variable, hopefully it won't
cause any big pref regression.
Comment 7 Peter Zavadsky 2002-05-28 14:20:47 UTC
Fixed in [trunk]

Fix:
core/../windows/frames/DefaultContainerImpl.java [1.58]
                       SplitContainerImpl.java [1.37]
                       MultiTabbedContainerImpl.java [1.37]

Note:
There was not enough synchronized access to topComps (now I renamed it
to topComponents) field in DefaultContainerImpl and its subclasses,
what led to the issue.
Comment 8 Milan Kubec 2002-06-03 12:03:21 UTC
Reopening, I reproduced it, with different component - Component
Inspector, after opening project imported from ffjce30. The project
was saved on GUI Editing WS.
Comment 9 Milan Kubec 2002-06-03 12:10:21 UTC
Created attachment 6038 [details]
exc stack trace with Comp. Inspector
Comment 10 Peter Zavadsky 2002-06-03 13:41:44 UTC
Fixed in [trunk]

Fix:
core/../windows/frames/MultiTabbedContainerImpl.java [1.40]

Note: This was another cause of exception (there was planned selecting
of component, and in case it is not contained, was choosen the last
one, but the data were taken from previous task, not current one, thus
could happen were in incosistent state).

Please create new issue necxt time, so we can differ the patches later.
Comment 11 Milan Kubec 2002-10-17 11:09:05 UTC
Verified.
Comment 12 Quality Engineering 2003-07-01 16:37:17 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.