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 76806 - Deadlock during CVS diff
Summary: Deadlock during CVS diff
Status: RESOLVED FIXED
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 5.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@editor
URL:
Keywords: RANDOM, THREAD
Depends on:
Blocks:
 
Reported: 2006-05-24 14:24 UTC by Marian Petras
Modified: 2007-11-05 13:44 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
full thread dump (26.97 KB, text/plain)
2006-05-24 14:25 UTC, Marian Petras 		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 Marian Petras 2006-05-24 14:24:15 UTC 
(NetBeans 5.0, Linux / Fedora Core 4, Intel PC, JDK 1.6.0-b84)

A deadlock occured after I asked the IDE to display a diff of the current file.

I right-clicked on the tab of a file (JUnitAntLogger.java) in the editor and
selected CVS|Diff.... A tab labelled "JUnitAntLogger.java [ Diff ]" was opened
and activated, a progress bar with title 'Diffing "JUnitAntLogger.java" ...'
appeared and the IDE froze.

According to the JRE, the freeze was caused by a deadlock:

Found one Java-level deadlock:
=============================
"Default RequestProcessor":
  waiting to lock monitor 0x08fe670c (object 0x8e7432a0, a java.lang.Class),
  which is held by "AWT-EventQueue-1"
"AWT-EventQueue-1":
  waiting to lock monitor 0x08fe6af4 (object 0x86fe45a8, a
org.netbeans.modules.editor.EditorModule$HackMap),
  which is held by "Default RequestProcessor"

I will attach a full thread dump.
Comment 1 Marian Petras 2006-05-24 14:25:15 UTC 
Created attachment 30586 [details]
full thread dump
Comment 2 Maros Sandor 2006-08-07 15:08:21 UTC 
I think this is an editor issue, please evaluate.
Comment 3 Vitezslav Stejskal 2007-02-15 01:32:47 UTC 
This should be now fixed after the changes made for fixing issue #92449.