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 97289 - Deadlock of KitsTracker and o.n.e.Settings
Summary: Deadlock of KitsTracker and o.n.e.Settings
Status: RESOLVED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: languages (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-06 15:18 UTC by Jan Jancura
Modified: 2007-03-07 09:56 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Deadlock (6.19 KB, text/plain)
2007-03-06 15:20 UTC, Jan Jancura
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Jancura 2007-03-06 15:18:47 UTC
Deadlock
Comment 1 Jan Jancura 2007-03-06 15:20:30 UTC
Created attachment 39210 [details]
Deadlock
Comment 2 Miloslav Metelka 2007-03-06 16:28:20 UTC
First I thought that it would suffice to use Settings.class for kitsTracker but
it would probably further deadlock on IC$ConvertingItem.
Comment 3 Vitezslav Stejskal 2007-03-06 23:20:17 UTC
Don't touch settings from your kit's constructor. You should implement
Settings.Initializer and register this implementation with
Settings.addInitializer and set the default values for your settings in
S.I.updateSettingsMap. It is safe to call S.addInitializer (and even S.reset)
during the kit's construction as it does not synchronize on Settings.class object.

I know the old editor settings infrastructure has its quirks and with hardly any
documentation it's not easy to guess how things should be done. I'll add this as
a usecase to Settings' javadoc.
Comment 4 Jan Jancura 2007-03-07 09:56:51 UTC
fixed.