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.
JFluid may run out of memory when exporting results in the call chain format, when pretty large files can be generated.
Reducing the priority - this feature is used very rarely, if at all, so this fix better gives way to more urgent issues for now.
Especially since with this release the profiler is required to be running on the same machine as the profiled JVM... it would really be nice to do the initial collection of profiling on that machine (high end shared application server machine), but then immediately save it off so that it can be analyed on another machine (developer's machine) -Jon
This depends on the way results are stored in memory -> dependency on the issue representing this
Changing the priority to match bug priority guidelines, changing target milestone to 4.1 to track this issue in the context of the release
The dependency that I am deleted was there probably by mistake. This issue is a pure defect issue, related to how creating the internal StringBuffer with data for export and then saving it in a file is done. It is "orthogonal" to the issue of how profiling results are stored in memory.
Fixed in M6 release.
old issue, closed