GNOME Bugzilla – Bug 353691
History handlers should be disabled by default because of the CPU consumption
Last modified: 2006-10-18 10:56:33 UTC
Please describe the problem: From time to time (ca every 5 minutes) deskbar-applet takes 90% of the cpuload. During this period it does not react to useractions like clicking the applet or pressing the shortcut. Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
Can you list what extensions you have enabled? And if, by selectively disabling some of them, can you make the symptoms disappear?
Hi, after a long time of testing (i disabled all plugins, and enabled them one after another), I think the "Web History" plugin ("Open your web history by name") is responsible for this ressource-attack.
We can't really do otherwise as it is. We need the browser to export a service allowing to search his history, and not parsing the xml file ourselves..
Then, in my opinion, the plugin shoud be disabled per default. Deskbar is not in a usable state when it does not react to input from time to time... Or am I the only one this problem occures? I'm using galeon as gnome default browser.
You are right that it should be disabled per default. Marking as such for next release.
Ah, Galeon. If I recall correctly, Galeon isn't really updated these days (there was a proposal for Galeon to be implemented as plug-ins on top of Epiphany), and none of the core Deskbar devs uses Galeon with any regularity. I think I wrote the original Galeon (XBEL??) parser really quickly without using Galeon itself for more than ten minutes (and hence on a really tiny history file). If we disable anything in a maintenance release, I would disable Web History *for Galeon only*. Ideally, someone would knuckle down with a real-world Galeon history file and bash Deskbar's parser into shape. Or at least profile to see where all the CPU is burning.
Nigel: This concerns all the history handlers, because they all do basically the same: the parse the (possibly huge) history xml file in memory. While you have generally less bookmarks to parse, so that's why i suggest we disable history reading..
Disabled for default in schema in CVS