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 65227 - [50cat] Starvation on Find in Toolkit.getSystemSelection
Summary: [50cat] Starvation on Find in Toolkit.getSystemSelection
Status: RESOLVED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 5.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Jaroslav Tulach
URL:
Keywords: THREAD
Depends on:
Blocks:
 
Reported: 2005-09-27 21:38 UTC by Unknown
Modified: 2008-12-22 20:32 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Thread dump (18.74 KB, text/plain)
2005-09-27 21:39 UTC, Unknown 		Details
Another thread dump (if helpful) (18.44 KB, text/plain)
2005-09-28 21:32 UTC, Unknown 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2005-09-27 21:38:33 UTC 
[ BUILD # : 200509251800 ]
[ JDK VERSION : 1.6 ]

3 times I've had a deadlock situation on Linux (Debian sarge)
java version "1.6.0-ea"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0-ea-b53)
Java HotSpot(TM) Client VM (build 1.6.0-ea-b53, mixed mode, sharing)
The first was after clicking on a result after Find Usages.  The last two were executing a Find in the current document.
I'll post the thread dump.
Comment 1 Unknown 2005-09-27 21:39:14 UTC 
Created attachment 25241 [details]
Thread dump
Comment 2 Jan Chalupa 2005-09-28 10:17:49 UTC 
Clipboard?
Comment 3 Unknown 2005-09-28 21:32:23 UTC 
Created attachment 25271 [details]
Another thread dump (if helpful)
Comment 4 Jaroslav Tulach 2005-09-29 10:26:42 UTC 
Not exactly clipboard, but system selection - we hacked clipboard to prevent  
deadlocks and time out, but we did nothing for system selection.  
  
I see nothing we can do to workaround the problem. Moreover I suspect there is  
something wrong in JDK as none of our threads are really participating in this  
starvation.  
 
I've reported a JDK bug 6330416 to track the problem.