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 210255 - Netbeans deadlocks on ctrl+z
Summary: Netbeans deadlocks on ctrl+z
Status: RESOLVED INCOMPLETE
Alias: None
Product: php
Classification: Unclassified
Component: Editor (show other bugs)
Version: 7.2
Hardware: PC Linux
: P3 normal (vote)
Assignee: Ondrej Brejla
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-28 10:36 UTC by paolosca
Modified: 2012-04-02 15:28 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description paolosca 2012-03-28 10:36:56 UTC
Product Version: NetBeans IDE Dev (Build 201203260401)
Java: 1.7.0_03-icedtea; OpenJDK Client VM 22.0-b10
System: Linux version 3.2.0-2-686-pae running on i386; UTF-8; en_US (nb)
User directory: /home/paolo/.netbeans/dev
Cache directory: /run/netbeans

Yesterday I installed the latest nightly build. Today, on one file, whenever I press ctrl+z do undo NetBeans deadlocks and I have to kill the process.

I tried to do a stacktrace but jstack says:

root@saturn:/home/paolo# jstack -F 3972
Attaching to process ID 3972, please wait...
Exception in thread "main" java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at sun.tools.jstack.JStack.runJStackTool(JStack.java:118)
	at sun.tools.jstack.JStack.main(JStack.java:84)
Caused by: java.lang.RuntimeException: Type "nmethodBucket*", referenced in VMStructs::localHotSpotVMStructs in the remote VM, was not present in the remote VMStructs::localHotSpotVMTypes table (should have been caught in the debug build of that VM). Can not continue.
	at sun.jvm.hotspot.HotSpotTypeDataBase.lookupOrFail(HotSpotTypeDataBase.java:362)
	at sun.jvm.hotspot.HotSpotTypeDataBase.readVMStructs(HotSpotTypeDataBase.java:253)
	at sun.jvm.hotspot.HotSpotTypeDataBase.<init>(HotSpotTypeDataBase.java:87)
	at sun.jvm.hotspot.bugspot.BugSpotAgent.setupVM(BugSpotAgent.java:568)
	at sun.jvm.hotspot.bugspot.BugSpotAgent.go(BugSpotAgent.java:494)
	at sun.jvm.hotspot.bugspot.BugSpotAgent.attach(BugSpotAgent.java:332)
	at sun.jvm.hotspot.tools.Tool.start(Tool.java:163)
	at sun.jvm.hotspot.tools.JStack.main(JStack.java:86)
	... 6 more

Not sure it's an issue of NetBeans or OpenJDK, but until now it never deadlocked so often.

Regards,

Paolo
Comment 1 Ondrej Brejla 2012-04-02 15:28:08 UTC
There is nothing from NetBeans packages...and using OpenJDK...it doesn't seem to be a NB bug. Incomplete until more info, or such.