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 68941 - Performance tests measuring complex starttup are failign
Summary: Performance tests measuring complex starttup are failign
Status: VERIFIED FIXED
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: issues@editor
URL:
Keywords: T9Y
Depends on:
Blocks:
 
Reported: 2005-11-18 16:24 UTC by Marian Mirilovic
Modified: 2007-11-05 13:44 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Full tread-dump (16.77 KB, text/plain)
2005-11-18 16:27 UTC, Marian Mirilovic
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marian Mirilovic 2005-11-18 16:24:20 UTC
It started on the build 200511161900 it did run without any problems in build
200511151900. 

Investigation:
I've found out that the lock file still exists when we try to start the IDE with
prepared userdir. The reason is that the preparation of the userdir(open
project, close Welcome, close Memory meter, open files) didn't finish
successfully, or the IDE is still running. After few attempts to fix it I found
that the Preparation just failed, it hass been killed by the xtest. Look at the
attachment, there is a full thread-dump from the IDE in that time.
Comment 1 Marian Mirilovic 2005-11-18 16:27:39 UTC
Created attachment 27051 [details]
Full tread-dump
Comment 2 Marian Mirilovic 2005-11-18 16:45:07 UTC
Editor guys please look at the thread-dump, there is more or less only the editor. 
Any suspicius fix between 200511151900 and 200511161900 ? 
Comment 3 Miloslav Metelka 2005-11-18 19:04:07 UTC
I have fixed issue 61103 in two stages and the last commit was done at 22:19
while the daily build was done at 19:00 so the fix was not included in the daily
build.
The BaseCaret.updateType() no longer calls dispatchUpdate() so I'm confident
that this deadlock no longer occurs. Marking as fixed, please reopen if I'm wrong.
Comment 4 Marian Mirilovic 2005-11-21 08:16:21 UTC
It looks like it really works in NB 5.0 (200511201900) - verified