|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
Ubuntu Oneiric, JDK 6u29 32-bit
Ubuntu Oneiric, JDK 6u29 32-bit
|
|
I get a bunch of UI freezes on Ubuntu in NetBeans related to this library, e.g. Tools > Options > Miscellaneous > JavaCard, which the self-profiler indicates result from sun.awt.X11GraphicsDevice.getCurrentDisplayMode taking several hundred msec per invocation. Consider whether these calls (e.g. from MultilineLabelUI.getMaximumSize) are really necessary. The resulting width value seems to only be used when there is no parent, and in this case does it matter what the minimum or maximum size is?
|
|
Description
|
I get a bunch of UI freezes on Ubuntu in NetBeans related to this library, e.g. Tools > Options > Miscellaneous > JavaCard, which the self-profiler indicates result from sun.awt.X11GraphicsDevice.getCurrentDisplayMode taking several hundred msec per invocation. Consider whether these calls (e.g. from MultilineLabelUI.getMaximumSize) are really necessary. The resulting width value seems to only be used when there is no parent, and in this case does it matter what the minimum or maximum size is? |
Show » |
Sort Order:
|
Bug
Open
Major
GraphicsDevice.getCurrentDisplayMode expensive
Not sure what it's used for if there's no parent; perhaps it should go away. At any rate, invocation of c.getGraphicsConfiguration().getDevice().getDisplayMode().getWidth() could be conditional on there being no parent; and the result could be cached (it would be incorrect if the screen resolution changes, but that's rare enough that we might choose not to care, or listen for changes in it if we want to be pedantic).
Or, for that matter, just using a value like 1024 or 1280 hard-coded would probably be fine enough.