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 114330 - CodeFoldingSideBar paint causes editor paint
Summary: CodeFoldingSideBar paint causes editor paint
Status: RESOLVED FIXED
Alias: None
Product: editor
Classification: Unclassified
Component: Code folding (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Miloslav Metelka
URL:
Keywords: PERFORMANCE
Depends on:
Blocks: 110302
  Show dependency tree
 
Reported: 2007-08-31 10:07 UTC by Marek Fukala
Modified: 2007-11-05 13:39 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
The profiler snapshot (534.32 KB, application/octet-stream)
2007-08-31 10:11 UTC, Marek Fukala
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marek Fukala 2007-08-31 10:07:07 UTC
The CFSB paint causes the editor content paint. Supposely this is just a measurement paint to resolve the CFSB position
and size (I am not able determine this from the callstacks). In any case the CFSB paint asks the editor HL to render
which slows down the paint and is IMHO unnecessary. I'll attach a profiler snapshot - just expand the AWT thread and the
CFSB callstack - about half of the AWT time is spend there.
Comment 1 Marek Fukala 2007-08-31 10:11:40 UTC
Created attachment 47867 [details]
The profiler snapshot
Comment 2 Vitezslav Stejskal 2007-09-06 14:35:43 UTC
First, I assume this was meant to be filed against 6.0. Second, rendering/painting is used for measurements from
modelToView and viewToModel and it involves highlighting layers, because their highlights may affect the size of
rendered text. IMO there is no other way around this, even though we should be able to optimize it so that it renders
only things that need to be rendered. One such optimization was done for issue #114016. Another one would be more
efficient view hierarchy (we may do that after nb6).

Please try it again, the situation should be much better now after fixing #114016.