Comment 2 for bug 132556

I am not sure if this is a duplicate of bug #122786. The (separate) issue with the radeon driver may very well be that bug (so thanks for pointing this out and I will have a look), but I think it remains the question why is evince putting so much load on the xserver during searching (in which graphically nothing but the progress count changes) to trigger this graphics bug and slow down the search it self?

(The rest of this comment is pure speculation so most likely wrong)
Could it be, that something during search is constantly causing a redraw of too much of the screen? In an attempt of profiling the problem, one of the highest ranking functions in evince was ev_view_expose_event. Although the actual time was somewhere in the sub permil range, so could very well be noise. Most time was spent in libfb.so (when using the radeon driver). Also I didn't have the debug symbols of poppler, as there doesn't seem to be a dbg package of it in the gutsy repository.

thanks for looking into this