Hi all,
The lazarus 0.9.26 working very slow with GTK2, I using fedora 8. I see my CPU working until 100% just working with the lazarus, such scroll, moving the components, etc.
Why,
thanks
dayat

Mailing lists / lazarus / 2009-01
5 messages · 3 people · –
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
Hi all,
The lazarus 0.9.26 working very slow with GTK2, I using fedora 8. I see my CPU working until 100% just working with the lazarus, such scroll, moving the components, etc.
Why,
thanks
dayat
There doesn't seem to be any implicit problem with F8 / GTK2 / 0.9.26 - it works OK for me. (I admit I use window$ more often). Perhaps you could give more details of your environment.
regards,
John Sunderland
The Fedora 8 running on VirtualBox 2.0.6 on Vista. For host machine I use 3GB RAM, and Core Duo CPU. Have virtualbox a problem.
Thanks John
dayat
dayat wroteThe Fedora 8 running on VirtualBox 2.0.6 on Vista. For host machine I use 3GB RAM, and Core Duo CPU. Have virtualbox a problem.
Run the top command on your VM and hit shift-P to sort on the process that are actually consuming the cpu. If you've installed the VirtualBox guest extensions, VBoxClient has been known to run away with the cpu. Top will also tell you if you're swapping. If kswapd is consuming a lot of cpu and you're using swap space, consider adding more ram to your vm.
You might also try upgrading to VirtualBox 2.1 that was recently released.
-Tom
Tom Lisjac wroteOn Fri, Jan 2, 2009 at 2:13 AM, dayat wrote: > The Fedora 8 running on VirtualBox 2.0.6 on Vista. For host machine I use > 3GB RAM, and Core Duo CPU. Have virtualbox a problem.
After taking a second look, there appears to be more to this then just vm configuration.
I set up the latest svn's for the ide and compiler on a well provisioned VirtualBox 2.1 vm running Fedora 10 and am seeing the same issue that the original poster described. Doing anything form related, such as dropping a new component or moving an existing one drives the cpu into saturation for many seconds. During that time, click events are dropped, form repaints aren't done and the process activity seems evenly divided between the ide and X. The huge Netbeans and Eclipse ide's run acceptably fast on this vm, so this issue isn't due to a lack of computing resources.
Trying to narrow it down, I removed all the Virtualbox guest extensions, went back to the generic vesa driver, toggled hvm support and tried running the ide as root... all with the same result. The same ide and compiler svn's run fine on a bare metal install of Fedora 10.
This is the first time I've seen an application that didn't run perfectly under VirtualBox and I'm curious what the underlying problem is. I'm planning to set up oprofile when I have some time to see where all those cpu cycles are going. If anyone has additional suggestions for troubleshooting this, I'll be happy to try them.
Thanks,
-Tom