I invoked commit on my project shared on kenai -> ide become blocked for about ten seconds, I was successfull to create
a threaddump some thread is working with sockets in AWT:
- locked <0x00007f56a0a7f518> (a sun.net.www.protocol.https.DelegateHttpsURLConnection)
Created attachment 82542 [details]
It looks like this project was not found in cache. It means that it was not touched before (e.g. loaded by dashboard)
> It looks like this project was not found in cache. It means that it was not touched before (e.g. loaded by dashboard)
however, we the commit shouldn't make that call in awt. will fix it.
*** Issue 166102 has been marked as a duplicate of this issue. ***
Created attachment 83002 [details]
patch - the default bug-tracking repository is now determined asynchronously
The routine that determines the issue tracking repository to be preselected is now called from a separate thread (using
RequestProcessor.getDefault()) so it does not block the AWT thread. The routine does not start until the Commit dialogue
is displayed (exactly: until it is made displayable). If the routine finishes its jobs successfully, the default
repository (as determined by the routine) is pre-selected in the Issue Tracker combo-box, unless the user had already
If the pop-up of the Issue Tracker combo-box is displayed at the moment the routine determines the default repository
and the user had not selected one themselves, the default repository is not selected as long as the pop-up is visible.
Then, if the user selects some repository from the pop-up, their selection is respected, i.e. not changed to the default
repository. If the user has not selected any repository from the pop-up, the the default repository is selected as soon
as the combo-box's pop-up is closed. UI experts, if you think you know of a better solution, please speak up.
Integrated into 'main-golden', will be available in build *200905310201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Marian Petras <firstname.lastname@example.org>
Log: fixed bug #165694 ("socket communication should not block AWT")
67patch1 ... fix of this issue is a part of changesets in issue 166591
The fix has been ported into the release67_fixes repository.