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 124511

Summary:	Connecting to target vm dialog blocks ui
Product:	profiler	Reporter:	_ tboudreau <tboudreau>
Component:	Ide	Assignee:	issues@profiler <issues>
Status:	REOPENED ---
Severity:	blocker	CC:	jglick
Priority:	P3	Keywords:	UI
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:

Description _ tboudreau 2007-12-29 20:46:11 UTC

I'm trying to profile a NetBeans based application;  it does not seem to be starting, so I would like to scroll down in the output window and see if there's any 
logging to explain what is wrong.  But I can't, because the "Connecting to target VM" progress bar is shown in a modal dialog.

Any reason this can't use the Progress API and not block the whole main window?

Comment 1 J Bachorik 2008-03-29 12:38:05 UTC

changing milestone

Comment 2 Jiri Sedlacek 2008-08-29 17:35:47 UTC

This doesn't seem to be a DEFECT - it works as designed. The main window is blocked intentionally to prevent the user
from invoking any other actions and/or modifying configurations. One of the reasons is that only one profiling session
can be running at a time.

If the profiler fails to connect, it timeouts after a while (for Profile Project). Or you can click the Cancel dialog.
In both cases you are then able to access the Output window to see what's wrong.

Feel free to file a RFE if you still think that connecting to profiled application shouldn't block the main window. In
such case please describe a real usecase which shows that this change is useful/necessary.

Comment 3 _ tboudreau 2008-09-02 16:29:21 UTC

> In both cases you are then able to access the Output window to see what's wrong.

Actually, the problem is specific to using the output window in "floating" mode - you cannot click its button at the bottom of the main window to see the 
output.

Comment 4 Jiri Sedlacek 2008-09-02 16:37:20 UTC

I see - you are able to access the Output as soon as the profiling session starts/fails, I don't think there's a strong
requirement to be able to access it during the few seconds while the profiler connects to the profiled application.
Anyway, the workaround is simple - dock the Output, I think that's exactly the intention of this feature.

Comment 5 _ tboudreau 2008-09-02 17:03:37 UTC

> In both cases you are then able to access the Output window to see what's wrong.

Actually, the problem is specific to using the output window in "floating" mode - you cannot click its button at the bottom of the main window to see the 
output.

Comment 6 Jesse Glick 2011-12-29 13:50:59 UTC

I am constantly bothered by this issue as well. I do not think using a modal dialog here is acceptable. I try to profile a Maven app and all sorts of potentially interesting output is being displayed in the Output Window, but not necessarily scrolling down, and I cannot get to the scrollbar because of this silly dialog.

(In reply to comment #2)
> only one profiling session can be running at a time

So? In the unlikely case that the user tries to start a second session while one is already running, just display an error dialog saying that this is not supported.