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: | FileMapStorage.getReadBuffer() called in EDT | ||
|---|---|---|---|
| Product: | platform | Reporter: | Egor Ushakov <gorrus> |
| Component: | Output Window | Assignee: | Jaroslav Havlin <jhavlin> |
| Status: | REOPENED --- | ||
| Severity: | normal | CC: | ilia, mentlicher, misterm, scanti |
| Priority: | P3 | ||
| Version: | 7.1 | ||
| Hardware: | PC | ||
| OS: | Solaris | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: | snapshot | ||
when I stopped debug session, IDE came back top speed This does not seem like a debugger issue. In the snapshot there's nothing that would indicate 100% CPU usage. The total time is 173.5 seconds and there is just one thread that spends that time on CPU: JDI Target VM Interface. But, most likely, it does nothing, it's just stuck on socketRead0(). The only thread that does something noticeable is AWT-EventQueue-1. But it spends only 28 seconds from 173.5. It's not debugger related at all, it does something in Output. Since it spends almost 17 seconds in FileMapStorage.getReadBuffer(), my guess is that the system is just swapping memory to/from disk. How large is the output in the Output Window? Did the program print something during the weekend? it may be the case, anyway strange that it reads from the disk even though I did not scroll or do anything in the output window, will give more details when it happen again. and the bug here is that it reads from the disk in EDT *** Bug 236289 has been marked as a duplicate of this bug. *** |
Created attachment 114458 [details] snapshot I started debug session, stopped on a breakpoint and went home for a weekend, when I came back 1 CPU was fully occupied and IDE was very slow. See attached snapshot