Bug 551151 - Modal "Terminate failed" popup often hidden behind "Hot Code Replacement Failed"
Summary: Modal "Terminate failed" popup often hidden behind "Hot Code Replacement Failed"
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.13   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-17 04:58 EDT by Mickael Istria CLA
Modified: 2023-09-01 15:45 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mickael Istria CLA 2019-09-17 04:58:24 EDT
I have a workflow where I see the "Hot Code Replacement Failed" pretty often. It's fine, I like it that way.
However, when I click terminate these days, I often get a "Terminate Failed" popup. It could be related to bug 544673 and it isn't really the issue of the current ticket.
The issue is that the "Terminate Failed" dialog is stacked *behind* the "Hot Code Replacement Failed" dialog (which remains open), so I get a feeling that the UI is totally frozen, until I think about moving the "Hot Code Replacement Failed" dialog and notice the active "Terminate Failed" popup behind. Then clicking OK brings everything back to normal.
In that case, the modal dialog should always be on top, or the "Hot Code Replacement Dialog" should close before the other popup shows up.
Comment 1 Sarika Sinha CLA 2019-09-20 01:53:18 EDT
Yes, I get the same problem during git pull many times. The dialog on top can not be clicked and it is not intuitive that you need to click OK in the dialog which is stacked behind.
Comment 2 Eclipse Genie CLA 2021-09-10 18:41:32 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Eclipse Genie CLA 2023-09-01 15:45:51 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.