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 194593 - NetBeans quits silently
Summary: NetBeans quits silently
Status: REOPENED
Alias: None
Product: platform
Classification: Unclassified
Component: Launchers&CLI (show other bugs)
Version: 7.0
Hardware: All All
: P3 normal (vote)
Assignee: Libor Fischmeistr
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-21 18:02 UTC by Thomas Preisler
Modified: 2016-03-10 10:31 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Preisler 2011-01-21 18:02:30 UTC 
If you attempt to start NetBeans and you already have one instance running, it tries to forward the already running NetBeans and then quits silently. It assumes the user will notice the forwarded IDE and understand the reason why it doesn't start one. Unfortunately, forwarding doesn't always work as intended leaving the user with no clue about why it didn't start. For instance if you are displaying on a second monitor, using VNC, Xhosting, and even on some systems natively because of bugs in Java/OS (see 194192), you may never get a chance to see the 'other' NetBeans leaving a frustrated user.

Firefox and other similar applications have solved this issue with a message like: An instance is already running, please ......". giving the user a clue of what is going on and what to look for.

I suggest Netbeans do something similar.

See also CR 7013050 Cannot start "solstudio" - it exits without any error message:
Comment 1 Jiri Rechtacek 2012-02-16 16:57:21 UTC 
Assigned to new owner.
Comment 2 Libor Fischmeistr 2012-03-29 09:13:56 UTC 
Hello Thomas,

I think you are right and there would be some notification that would inform user there is already running instance of NB. But actual state how it works is correct how it was planned. It has taken a lot of time to Jaroslav Tulach to make it work. So I believe it wouldn't be good to fix it as a bug.

We will discuss it internally and consider to bring it into some future version of NB.

I don't consider it as bug, it may be enhancement.

Thank you for your report.

Some information about this issue you can find here: issue 32054
Comment 3 Alexander Simon 2014-08-06 14:51:07 UTC 
Solaris Studio bug still exists.
It is time to reevaluate the issue.
Comment 4 Alexander Simon 2016-03-10 09:41:33 UTC 
I do not see the fix.
Comment 5 Vladimir Kvashin 2016-03-10 10:31:56 UTC 
(In reply to Alexander Simon from comment #4)
> I do not see the fix.
Alexander, "WORKSFORME" status does *not* assume the fix.

Could be the fix as simple as reporting in console that there is another instance and, if possible, its PID? I think if we can do so and (ideally the message should be printed directly to console, not just to the message log), then this will solve the issue for guys who reported it.

I think this is important mostly for Unix guys. 
And these guys tend to launch programs from console.
I thin we can ignore Windows in this respect.

Libor, do you think fixing it that way is possible?
Alexander, would you agree with such fix?