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.
Summary: | IDE Locks up entirely | ||
---|---|---|---|
Product: | platform | Reporter: | Mark Crouch <mcnicusa> |
Component: | -- Other -- | Assignee: | Tomas Hurka <thurka> |
Status: | VERIFIED WORKSFORME | ||
Severity: | blocker | CC: | mmirilovic, thurka, ttran |
Priority: | P2 | Keywords: | THREAD |
Version: | 3.x | ||
Hardware: | Macintosh | ||
OS: | Mac OS X | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Java Crash Log |
Description
Mark Crouch
2002-09-25 14:09:48 UTC
We need more information : NB version,number, JDK version,number, after freeze create full thread-dump, ..... I close this issue as INVALID, without additional info we cannot do nothing. Please add appropriate informations and reopen this one, thanks? Here is the requested info: NB version - 3.4 JDK version - 1.3.1 I was unable to obtain a thread dump. The process(java) was hanging, taking up 100% CPU. I issued a "kill -QUIT" signal to the process, but the process remained active for over 10 minutes. I was then forced to issue a "kill -9(KILL)" to take the process down hard. This is the second time the ide has frozen today!!! The second time, the ide had only been started for about 2 minutes! Please let me know if there is an easier way in Mac OS X to produce the thread dump you requested. Thanks. Mark C. cc'ing Tomas H. - because he is the only one person who has Mac under his table. Tomas, can you answer last question ? Thanks advance. The IDE has once again locked up on me. I need to know if someone can help me create a thread dump on Mac OS X(10.1.5). When I issue the "kill -QUIT" command to the "java" process, the process continues to hang and never dies. I have to bring it down hard with a "kill -9". I cannot provide more information until I get assistance with this issue!!! Thanks! Mark C. I don't know how, but Tomas will know, wait till tomorrow. Mark, how did you run NetBeans? From Terminal or with NetBeansLauncher? Anyway kill -QUIT produces thread dump, so you are doing it correctly. If you are running NetBeans from Terminal you can produce thread dump by ctrl-\ in Terminal window, but it does the same as kill -QUIT. I started netbeans by way of the Netbeans Launcher. I am aware that "kill -QUIT" produces the thread dump, however I am at a loss as to where the dump file is produced. I started the console and there was no dump log for netbeans visible. Please let me know where I may find this dump file and I will be happy to send it to you. Thanks Mark C. If you are using NetBeans Launcher, the thread dump is in /var/tmp/console.log . This file is also accessible via /Applications/Utilities/Console.app Mark, another question. Which version of Mac OS X are you using and what is your hardware configuration? There seems to be a problem where the interface locks up when using hardware acceleration in java with the Rage 128 Pro (16MB) on Mac OS X 10.2 Created attachment 7543 [details]
Java Crash Log
I have experienced more occurences of lockups with the IDE today. I must say that my level of frustration with Netbeans 3.4 on Mac OS X is getting very high. At this time, I can't see even using this product on Mac OS X until these fundemental problems are solved. Is there a setting in the JVM that would solve this problem, or is it something in the IDE code? I don't understand why this problem cannot be recreated on your side. I have a very generic out of the box Mac OS X 10.1.5 setup. Today when the IDE froze up, I was again unable to kill the process with -QUIT and create a crash log. I again had to take the process down hard with kill -9, so no thread dump was produced. I am not sure how I can assist you further. Mark C. I am assigning this to Tomas Hurka for investigation. please always add THREAD keyword to issues related to deadlock Mark, I am sorry, but without thread dump we are not able to investigate it. I am not able to reproduce it on Mac OSX 10.2.3. Closing as works-for-me. Please, reopen if you have thread dump or reproducible test case. Thanks. Without new infromations for long time - verifying. |