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 206712 - FileMapStorage.getReadBuffer() called in EDT
Summary: FileMapStorage.getReadBuffer() called in EDT
Alias: None
Product: platform
Classification: Unclassified
Component: Output Window (show other bugs)
Version: 7.1
Hardware: PC Solaris
: P3 normal (vote)
Assignee: Jaroslav Havlin
: 236289 (view as bug list)
Depends on:
Reported: 2011-12-26 09:01 UTC by Egor Ushakov
Modified: 2017-01-31 15:18 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

snapshot (26.56 KB, application/octet-stream)
2011-12-26 09:01 UTC, Egor Ushakov

Note You need to log in before you can comment on or make changes to this bug.
Description Egor Ushakov 2011-12-26 09:01:34 UTC
Created attachment 114458 [details]

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
Comment 1 Egor Ushakov 2011-12-26 09:02:00 UTC
when I stopped debug session, IDE came back top speed
Comment 2 Martin Entlicher 2012-01-02 17:02:34 UTC
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?
Comment 3 Egor Ushakov 2012-01-10 10:39:09 UTC
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.
Comment 4 Egor Ushakov 2012-01-10 10:42:58 UTC
and the bug here is that it reads from the disk in EDT
Comment 5 Jaroslav Havlin 2013-09-24 08:42:54 UTC
*** Bug 236289 has been marked as a duplicate of this bug. ***