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 159296

Summary:	Debugging can make NB grind to a halt
Product:	php	Reporter:	rjt <rjt>
Component:	Debugger	Assignee:	rmatous <rmatous>
Status:	RESOLVED DUPLICATE
Severity:	blocker
Priority:	P2
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:

Description rjt 2009-02-27 10:52:46 UTC

I've been trying to debug some code executed in a loop, looping through an array of several hundred data. I'd like to be
able to set a conditional breakpoint so that I only begin debugging when I hit a certain element in the array (I know
that a conditional breakpoints issue has already been entered into IssueZilla), but given that this isn't yet supported,
I tried just setting the breakpoint and hitting Play on each iteration. After about the third iteration the IDE has
ground to a halt - the window doesn't repaint at all and memory consumption is up to 480MiB (or 377.1/377.1MB as
reported by the app's chart).

Comment 1 rmatous 2009-03-13 17:38:04 UTC

Please, could attach a code and give me instructions how to reproduce

Comment 2 rjt 2009-03-13 18:05:06 UTC

Yep, I'll build and attach a test-case....

Comment 3 rmatous 2009-03-13 18:14:35 UTC

great, thanks

Comment 4 rmatous 2009-03-24 22:08:38 UTC


*** This issue has been marked as a duplicate of 160956 ***