Comment 25 for bug 1219794

I'm trying to find the origin on these performance problems; already found 2 :

-> _when moving the cursor around_ (in text edit mode at least, probably in other tools as well), a list of all elements was computed at each mouse move[goal: to show the right cursor]. I pushed a fix for this (caching the list) in r14655. I'm not sure what the gobble fix proposed here does (if i understand correctly it "loses" the next same events, relieving a bit the cpu from that task), it might still be useful in addition, but i don't think so.

-> _when typing_, we spend a large amount of time recomputing the ... scrollbar length.
To do that, we compute (recursively) all bboxes in the document (because we want the root bbox), which are not well cached either, all that because "potentially" the edit has made the root bbox change, so the scrollbar "may" have to change. I might look for a way to fix that, not sure how yet (prevent "modified" signals when editing text, maybe?)

-> There must be other problems