Bug 577859 - RCP product not closed in debug but eclipse closed.
Summary: RCP product not closed in debug but eclipse closed.
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.21   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-17 00:59 EST by Batuhan Doğan CLA
Modified: 2023-12-17 15:02 EST (History)
3 users (show)

See Also:


Attachments
ini file (747 bytes, text/plain)
2021-12-17 02:47 EST, Batuhan Doğan CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Batuhan Doğan CLA 2021-12-17 00:59:52 EST
When i debug rcp product it works fine but, sometimes product doesn't response and eclipse closed but the product is not closed.
Comment 1 Batuhan Doğan CLA 2021-12-17 01:15:24 EST
by the way i am working with eclipse ide for commiters version: 2021-09 (4.21.0)
Comment 2 Batuhan Doğan CLA 2021-12-17 02:47:32 EST
Created attachment 287702 [details]
ini file

eclipse ini file is on the attached.
Comment 3 Sarika Sinha CLA 2021-12-17 03:35:35 EST
Can you provide reproducible steps?
Without that, the problem can not be analyzed.
Comment 4 Batuhan Doğan CLA 2021-12-17 05:54:18 EST
(In reply to Sarika Sinha from comment #3)
> Can you provide reproducible steps?
> Without that, the problem can not be analyzed.

what do u mean by reproducable steps? sorry i couldn't get. do u mean what are the steps that give rise to crash
Comment 5 Sarika Sinha CLA 2021-12-26 23:52:02 EST
(In reply to Batuhan Doğan from comment #4)
> (In reply to Sarika Sinha from comment #3)
> > Can you provide reproducible steps?
> > Without that, the problem can not be analyzed.
> 
> what do u mean by reproducable steps? sorry i couldn't get. do u mean what
> are the steps that give rise to crash

Yes.
Comment 6 Eclipse Genie CLA 2023-12-17 15:02:18 EST
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.