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 17464 - Deadlock when I start IDE (after shutdown IDE with running prog).
Summary: Deadlock when I start IDE (after shutdown IDE with running prog).
Status: CLOSED DUPLICATE of bug 17466
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P1 blocker (vote)
Assignee: David Simonek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-09 12:15 UTC by Richard Malaschitz
Modified: 2008-12-23 09:35 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
hs_err_pid2108.log (8.82 KB, text/plain)
2001-11-09 12:48 UTC, Jan Becicka 		Details
Thread-dump when hung (11.26 KB, text/plain)
2001-11-09 14:15 UTC, Jan Chalupa 		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 Richard Malaschitz 2001-11-09 12:15:14 UTC 
[JDK 1.4 b85]

Scenario:
- I shutdown IDE when some program is running (for example 
[sampledir]/examples/clock/ClockFrame)
- start IDE
- click on [Editing] or [GUI Editing] - IDE will be frozen
Comment 1 Jan Becicka 2001-11-09 12:46:01 UTC 
It looks like this bug does not occure on Solaris (at least we cannot 
reproduce it on this platform).
However it is 100% reproducible on Windows.
Sometimes this bug even cause crash of VM. See attachment.
Comment 2 Jan Becicka 2001-11-09 12:48:27 UTC 
Created attachment 3340 [details]
hs_err_pid2108.log
Comment 3 Jan Chalupa 2001-11-09 14:15:52 UTC 
Created attachment 3345 [details]
Thread-dump when hung
Comment 4 _ ttran 2001-11-09 14:24:28 UTC 
several issues are mixed together here:

The crash is a duplicate of #17283, bug in JDK 1.4.0 beta 3 (build 84)
on Windows.  The workaround is implemented but activated only for this
specific version of the JDK ["1.4.0-beta3-b84"].  Should we activate
it also for Sun internal builds which are not available to the public?

The deadlock is a separate issue.
Comment 5 Jan Chalupa 2001-11-09 15:04:15 UTC 
Removing the JDK_1.4 keyword. I've successfully reproduced the dead-
lock on 1.3.1 as well.
Comment 6 Jan Zajicek 2001-11-09 16:01:02 UTC 
This issue is about the deadlock not about the jvm crash that's a
duplicate.
Comment 7 Petr Hrebejk 2001-11-09 16:12:09 UTC 
For resolution of the JVM please see #17283. The fix is intentionaly 
set to work with the public beta of JDK 1.4 only, to see when first 
build of JDK with the bug fixed comes. Does anybody think that we should
enable it for all 1.4 - RCs (I don't)

As this bug is declared to be about the deadlock by Jan Zajicek. I'm
reassigning it to Window system. The deadlock seems to be caused by 
ModeData.Impl. 

This issue looks similar to #17464 althogh the threaddump is little
bit different.
Comment 8 Jan Becicka 2001-11-09 16:39:51 UTC 
As this bug is declared to be about the deadlock by Jan Zajicek, I'm 
setting priority to P1.
Comment 9 Jan Zajicek 2001-11-09 16:55:09 UTC 
After investigation of ftd this is a duplicated of already addressed
issue.

*** This issue has been marked as a duplicate of 17466 ***
Comment 10 Quality Engineering 2003-07-01 15:46:05 UTC 
Resolved for 3.4.x or earlier, no new info since then -> verified.
Comment 11 Quality Engineering 2003-07-01 16:43:59 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.