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 246992 - netbeans PID not in activity monitor but blocking OSX restart
Summary: netbeans PID not in activity monitor but blocking OSX restart
Status: NEW
Alias: None
Product: platform
Classification: Unclassified
Component: Launchers&CLI (show other bugs)
Version: 8.0
Hardware: PC Mac OS X
: P3 normal with 2 votes (vote)
Assignee: Libor Fischmeistr
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-10 13:19 UTC by Antonin Nebuzelsky
Modified: 2015-03-16 14:57 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 Antonin Nebuzelsky 2014-09-10 13:19:37 UTC
This report is based on user feedback on nbusers list:

(1)

-------- Original Message --------
Subject: [nbusers] Netbeans 8.0 Bug in Mac OS X Mavericks
Date: Mon, 1 Sep 2014 04:31:10 +1000
To: nbusers@netbeans.org

When I try to quit netbeans:
- the main window closes BUT
- the dock icon indicates it is still open
- it will not force quit
- I cannot reopen netbeans (error -600)
- I cannot find netbeans PID in activity monitor to execute kill command
- I cannot shutdown my computer without force restart. 

I love Netbeans, and use it as my primary development tool. But I can't put up with the required force restarts after using it :( 

Any help would be greatly appreciated. 

Note: I have tried reinstalling both netbeans and the latest java, with no avail. 

Kind Regards, 
Angus

---

(2)

-------- Original Message --------
Subject: [nbusers] Re: Netbeans 8.0 Bug in Mac OS X Mavericks
Date: Mon, 8 Sep 2014 08:40:47 +0000 (UTC)
To: nbusers@netbeans.org

I have exactly the same problem. It appeared a couple of days ago, and
I am not able to restart OS X without doing a physical hard reset.

The symptoms are:
- jps -m does not show the process
- When netbeans is open, it is possible to quit it (or kill -9 it
through the command line). None of these options make the icon
disappear from the command-tab process switcher
- After having quit netbeans, if trying to start it again OS X gives an
error message: "The applications NetBeans 8.0.ap can't be opened. -600"
-> the only way to start netbeans again is by doing a hard reset after
which it fires up.
- The behaviour is completely consistent and repeatable (annoyingly so,
I now have a process that I can't get to disappear lying around).

Please let me know if I can do any investigation or error checking. I
should be able to follow instructions :)

Søren
Comment 1 sorenvind 2014-09-22 09:35:43 UTC
Additional information:
- I discovered that the same thing can happen to Firefox or OS X (basically the same description as previously). 
- Therefore, this seems more like an OS X problem, or some other piece of software that is conflicting.

I tried closing applications one by one, and eventually both Firefox and Netbeans had disappeared as open programs. I am pretty sure the culprit was Tunnelblick, which I've only recently started used as an OpenVPN client. Is it possible that a collision with open files or sockets can cause this behaviour?

The above solution is at least a workaround to the issue (which was totally reproducible). 

Søren
Comment 2 a_laksmana 2015-01-07 10:48:13 UTC
Hi

When Netbeans started in Mac, it creates 2 processes pid: bash and netbeans. When you kill netbeans, it does not kill the parent bash. So all you need to do is to kill the parent process.

You can use Activity Monitor to find the parent (bash) pid and kill it.
Comment 3 Libor Fischmeistr 2015-03-16 14:57:35 UTC
(In reply to a_laksmana from comment #2)
> Hi
> 
> When Netbeans started in Mac, it creates 2 processes pid: bash and netbeans.
> When you kill netbeans, it does not kill the parent bash. So all you need to
> do is to kill the parent process.
> 
> You can use Activity Monitor to find the parent (bash) pid and kill it.

That should be suitable workaround. Thanks for it.

Decreasing priority to P3. If the workaround doesn't work increase back the priority.