Re: [[email protected]: Commit 3626. Redraw problems]
Johannes Hofmann <[email protected]>
| Newsgroups | gmane.comp.web.dillo.devel |
|---|---|
| Message-ID | <[email protected]> |
That was me. Sorry I didn't follow this. Can you point me to the problem? The idea with redrawY is that when loading long pages we don't keep redrawing the currently visible (top) part of the page while adding text on the bottom. Obviously this only works as long as the newly incoming HTML doesn't affect the layout of the already drawn (top) part of the page. Cheers, Johannes Am 24.04.2014 14:44 schrieb Sebastian Geerken <[email protected]>: On Wed, Apr 23, 2014, Sebastian Geerken wrote: > Hi Jorge, > > Today I saw commit 3626, and checked whether the pages I see to > > produce redraw storms and CPU hogs were gone, and... no :-P > > > > I got one of them and worked reducing it to try to produce a good > > test case, that's the attachment. If you open it with embedded CSS > > disabled, it's OK, then enable it and voila: redraw storm and CPU > > hog. > > > > I hope this helps the cause. Please let me know whether you can > > work on it, or give me some clues to try to start digging further. > > Yes, I can reproduce the problem. Thanks for the test. > > This change (revision 3626) was for the opposite problem: in some > cases, there is no redraw. It seems that I'll have to care about the > TODO of the commit message soon: "Cleanup and document lastWordDrawn > and redrawY!". > > I'll work on this soon, after an issue I'll hope to finish today. I'm now working on this, and have already found out that this is not a redrawing problem: the only change in 3626 is that the CPU load is shifted from dillo to Xorg. (It seems that more redrawing is done, but this is rather a symptom of another problem, probably with resizing.) I noted this several times, so please observe CPU load (e. g. with top(1)): if it stays high, even if dillo is responsive this is a problem you should send to the list. Sebastian PS: Cleaning up lastWordDrawn/redrawY is still an issue, but with lower priority. Who did actually implement this? _______________________________________________ Dillo-dev mailing list [email protected] http://lists.dillo.org/cgi-bin/mailman/listinfo/dillo-dev _______________________________________________ Dillo-dev mailing list [email protected] http://lists.dillo.org/cgi-bin/mailman/listinfo/dillo-dev