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: | Every node change calls potentially expensive NbClipboard.getContents() | ||
---|---|---|---|
Product: | platform | Reporter: | ebakke |
Component: | Explorer | Assignee: | Jan Peska <JPESKA> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 7.4 | ||
Hardware: | PC | ||
OS: | Mac OS X | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | .npss file attached from NetBeans |
Description
ebakke
2014-03-14 22:56:30 UTC
Created attachment 146035 [details]
.npss file attached from NetBeans
.npss file
OK, I'm definitively able to reproduce the sluggishness in the regular NetBeans IDE now, not just from my platform application. With a 4000x4000px image copied from Photoshop to the clipboard, moving up and down the nodes in the "Projects" tab with the keyboard becomes sluggish. Attaching an IDE profiling snapshot, taken while moving quickly between nodes in the projects tab. Look at the "Hot Spots" to find ActionStateUpdater.updateTrans() consume 36 seconds (due to calls to NbClipboard.getContents). Hmm, it gets worse. Applications like Excel expose text on the clipboard not only as text, but as a bitmap image as well, and NbClipboard.getContents appears to load the data in the image as well. Sometimes these images can get quite large, slowing down node selection in NetBeans (and causing OutOfMemoryErrors in my platform application). So this problem is more generally applicable than just for people who happen to be using Photoshop. *** This bug has been marked as a duplicate of bug 233513 *** |