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.
When using NetBeans 7.0 RC 1, it will freeze and require a force quit when editing CSS files — this sometimes happens immediately upon opening the CSS file, and sometimes takes up to 20 minutes, but I have yet to run NB for more than a half hour or so with a CSS file open without a freeze. I've let it spin for up to 10 minutes before performing a force quit to see if it would resolve itself. No luck. The issue isn't occurring on NetBeans 6.8 on my machine if that means anything.
Could you please generate thread-dump at time of the freeze, attach it here and reopen this issue ? http://wiki.netbeans.org/GenerateThreadDump Thanks in advance.
Created attachment 107888 [details] Thread dump at time of freeze
I'm not the original reporter, but I've been experiencing this as well on 6.9.1, 7.0rc2 and 7.0 The attached thread dump is from 7.0 that I downloaded this morning.
There appears to be no deadlock in the thread dump. Could you please attach your message.log file http://wiki.netbeans.org/FaqLogMessagesFile ? Thanks.
Created attachment 108062 [details] messages.log after freeze This isn't from the same time as my previous thread dump, but after I reproduced this behavior today.
There does not seem to be anything really problematic in the log file. Could you please check whether it's a deadlock or CPU at 100% and possibly attach some more thread dumps? Thanks.
Created attachment 108166 [details] OS X output to send to Apple
I am having this exact same problem. Netbeans 7.0 freezes upon opening a .css file, or when the CSS builder windows open while a .css file is open. I've attached the output I've received from OSX that it wants to send to Apple once I force close it.
marshallbu: Please attach a thread-dump as described http://wiki.netbeans.org/GenerateThreadDump Is CPU idle or at 100%?
Created attachment 108196 [details] Thread Dump during freeze when messing with .css My CPU is idle, java currently taking up ~2%, 442MB ram
Created attachment 108287 [details] Thread dump at time of freeze Thread dump taken while Netbeans unresponsive. CPU usage: 2.3%, RAM: 606.3MB
All, Want to add to this... the css-random-lock is killing my productivity. I just migrated from a 2009 MacBook Pro 15" running a fully updated Snow Leopard and using Netbeans 6.9.1 full-stack with no issues at all for as long as I've had it installed. Just got a new 2011 MBP 15" i7 model with a fresh, factory install and fully updated Snow Leopard build and installed a fresh copy of the 6.9.1 full-stack on it and ran into this bug within hours of setup. When the freeze occurs, I'm unable to get any type of JVM process monitoring or stack tracing tool to bind to the running Netbeans process... even when I run Netbeans from the command line. A Force-Quit or kill needs to be done to end the process. Here's my java -version dump: java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07-334-10M3326) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02-334, mixed mode) Should I open this in a 6.9.1 ticket or should we track it here? Also, if there's any other think I can try to get it to give me a clean trace, just let me know. Happy Hunting, Etienne
No, it's not necessary to file any other issue since this does not depend on NB version it happens in the same way either in 7.0 or 6.9.1. The thread dumps do not show any apparent deadlocks or problems so it's likely something wrong in the JVM. Reassigning to jdkproblems for further evaluation.
Obviously a bug in Apple JDK. Please, see http://developer.apple.com/bugreporter/bugbestpractices.html#Java and file the problem against Apple. Closing the bug on our side as wontfix.
For anyone looking for a work-around to this issue (who can't wait for an indeterminate amount of time for the OSX jdk to be fixed), I've resolved this by disabling code-folding... haven't had a crash in css, js or xml files since doing so. I'm a bit annoyed that this issue has been so easily written off as a Mac jdk problem as I never had this happen in NB 6.8's css/js/xml editors and I was using that version of NB all the way up until about 6 weeks ago. Seems to me that the way it's manifesting could be an issue in both implementation and the jdk that implementation is running on. Word, Etienne
Well said Etienne, I completely and wholeheartedly agree with your statement. I'm going to try your workaround to see if I have success.
v/c
After using Etienne's work around for the last month, by turning off code folding, haven't had a single crash since. Guess we'll have to wait on "Apple" to release some magic code folding fix for Netbeans ;-)
I also tried turning off code folding, but later turned it back on & haven't had NB freeze up since. I have become somewhat reluctant to open CSS files though, so that may not be an indication that it has resolved itself.