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 74397

Summary:	Should be able to filter classes when starting Memory Profiling
Product:	profiler	Reporter:	_ gsporar <gsporar>
Component:	Base	Assignee:	issues@profiler <issues>
Status:	RESOLVED DUPLICATE
Severity:	blocker
Priority:	P3
Version:	5.x
Hardware:	All
OS:	All
Issue Type:	ENHANCEMENT	Exception Reporter:
Attachments:	SJS AS 8.2 log file

Description _ gsporar 2006-04-04 18:50:49 UTC

When choosing to do Memory Profiling it would be very helpful if class filters
could be specified, much the same way they can be specified on Performance
Profiling.  This would make it much easier to do memory profiling of large
applications - the user could exclude classes that are not suspected to be
causing any memory problems, thereby reducing instrumentation overhead. 
Alternatively, the user could include only those classes that are suspected of
causing problems, thereby preventing instrumentation of all other classes.

Comment 1 Jiri Sedlacek 2006-04-05 10:42:37 UTC

Already filed as Issue 55474. FYI, I've just added this RFE to no1 priorities 
list for Profiler 6.0.

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

Comment 2 _ gsporar 2006-04-05 22:25:53 UTC

Created attachment 29648 [details]
SJS AS 8.2 log file

Comment 3 _ gsporar 2006-04-05 22:34:22 UTC

Oops... browser (or user :-) ) error - the attachment was intended for 74259....