Bug 485857 - Conditional breakpoints Memory leak
Summary: Conditional breakpoints Memory leak
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.4.2   Edit
Hardware: PC Windows 7
: P3 major with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-14 10:18 EST by Frank Gasdorf CLA
Modified: 2022-11-10 20:05 EST (History)
1 user (show)

See Also:

Attachments
simple test class to reproduce memory leak (381 bytes, application/octet-stream)
2016-01-14 10:18 EST, Frank Gasdorf CLA 		no flags Details
View All 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 Frank Gasdorf CLA 2016-01-14 10:18:12 EST 
Created attachment 259186 [details]
simple test class to reproduce memory leak

Having conditional breakpoint with an object reference causes Java heap exceptions. 

Exception in thread "main" java.lang.OutOfMemoryError: Java heap space

The garbage collecton doesn't release these objects.

Simple code to reproduce if Breakpoint is enabled in attached file (DebugBreaker.java).

Breakpoint conditon for Breakpoint in line 14:

   System.out.println(i.toString());
   return false;
Comment 1 Eclipse Genie CLA 2020-09-02 11:52:24 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 2 Eclipse Genie CLA 2022-11-10 20:05:51 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.