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 130190 - slow scrolling
Summary: slow scrolling
Status: RESOLVED WORKSFORME
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@editor
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2008-03-14 19:46 UTC by urlwolf
Modified: 2008-04-17 14:36 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description urlwolf 2008-03-14 19:46:45 UTC
I have a very strange problem with scrolling code. 
It's really slow and clunky; the CPU gets almost full use when scrolling too.
This just started happening. I'm using netbeans ruby.

I think the problem started when I installed 6.1 in a different folder (netbeansEdge).

I have netbeans working on a different computer and the scroll works just fine.
The install that is giving me problems is a clean one, 6.0.1, no user configuration (I deleted the files in .netbeans).

Any idea about why this is happening?

Thanks!
Comment 1 Vitezslav Stejskal 2008-03-15 17:07:06 UTC
Could you please attach here some thread dumps generated when the IDE is unresponsive? There is a wiki page describing
how to generate a thread dump - http://wiki.netbeans.org/GenerateThreadDump. Thanks a lot
Comment 2 pribyl 2008-04-17 14:36:11 UTC
Product Version: NetBeans IDE 6.1 RC2 (Build 200804170002)
Java: 1.6.0_10-beta; Java HotSpot(TM) Client VM 11.0-b11
System: Windows XP version 5.1 running on x86; Cp1250; cs_CZ (nb)

I am not sure how to reproduce this. I opened some ruby application, but I did not notice any scrolling problem.

I am closing this issue as we don't have any additional info for more than month. 

Urlwolf, please, if you can provide some concrete information what are you doing when this problem occur, feel free to
reopen. And the thread dump, as vstejskal suggested, should be also helpful.

Thanks