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: | netbeans PID not in activity monitor but blocking OSX restart | ||
---|---|---|---|
Product: | platform | Reporter: | Antonin Nebuzelsky <anebuzelsky> |
Component: | Launchers&CLI | Assignee: | Libor Fischmeistr <lfischmeistr> |
Status: | NEW --- | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 8.0 | ||
Hardware: | PC | ||
OS: | Mac OS X | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Antonin Nebuzelsky
2014-09-10 13:19:37 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 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. (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. |