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.
Summary: | Output Window Performace is bad due to stack trace logging | ||
---|---|---|---|
Product: | platform | Reporter: | lkishalmi <lkishalmi> |
Component: | Output Window | Assignee: | _ tboudreau <tboudreau> |
Status: | VERIFIED INVALID | ||
Severity: | blocker | Keywords: | PERFORMANCE |
Priority: | P4 | ||
Version: | 4.x | ||
Hardware: | PC | ||
OS: | OS/2 | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
lkishalmi
2004-08-31 15:56:47 UTC
I can probably just turn off use of memory mapped files on OS/2. It means all output will be stored on the heap, which means more heap usage, but should not be a problem unless the output is huge. I've digged a bit more, as I've noticed that the STDOUT/STDERR was redirected to a temporary file. So the problem is not that that STDOUT/STDERR couldn't be memory mapped. I also checked the OS/2 file api and there I've found the solution. I'm using a RAM file system for temporary files. Files on this file system doesn't support memory mapping. When I set the temp dir to a standard filesystem, the exceptions were gone, and the performance is good again. Tim, thanks for the short response! closed |