Bug 19792 - Canvas clock disappears after about 1 minute
Summary: Canvas clock disappears after about 1 minute
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL: http://www.station59.com.au/dev/kruna...
Depends on:
Reported: 2008-06-27 08:59 PDT by R Bassett
Modified: 2009-07-28 06:52 PDT (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description R Bassett 2008-06-27 08:59:29 PDT
Leave clock running for about 1 minute - the hands render wrongly then the whole clock disappears. I'm running GtkLauncher using webkit 34798 on gtk etc on x11 on a Fedora 8 Linux PC. It runs fine (i.e. as expected) in Safari 3.1.2 (525.21) on a Windows PC.
Comment 1 Dirk Schulze 2008-06-27 23:57:09 PDT
No problems with build 34833 here. Looks the same like in Safari.
Comment 2 R Bassett 2008-07-01 05:04:54 PDT
I tested it again on 34833 checked out from subversion and the clock still disappears after a minute or so. What system did you test it on? gtk? Fedora? It would be useful to perhaps locate differences in the build to see where a problem may lie. I built it using autogen.sh and make. Could it be a difference in cairo / gtk etc versions on the platform?
Comment 3 Dirk Schulze 2008-07-01 06:07:22 PDT
I build it with ./autogen.sh --with-http-backend=soup and libsoup from svn on ubuntu (WebKitGtk). I don't believe, that it is a problem of curl/soup, but I don't know.
Which version of cairo do you use? It's 1.6.0 for me. 
Comment 4 R Bassett 2008-07-02 01:51:35 PDT
On the Fedora 8 platform it is cairo 1.4.14, pixman 0.9.6, gtk+ 2.12.8 (running on X), and on a different platform which takes between 6 and 24 hours to go wrong (rather than minutes) which uses cairo 1.6.4, pixman 1.0.0 and gtk+ 2.12.9 (running on DFB). Ok so looks like there has been an improvement in cairo or gtk but not a total fix. I shall upgrade my PC to use a later fedora core as it looks like cairo 1.6.x etc is not being released for core 8, and then test again. 
Comment 5 R Bassett 2008-07-21 05:22:47 PDT
Sorry for the lack of progress update on this, I've failed to upgrade my PC to use the latest cairo for various reasons and its unlikely to happen before I leave this job, so best to close this bug and if someone else finds it later, to reopen / create a new one.
Comment 6 Dirk Schulze 2009-07-28 06:52:23 PDT
This bug is hopefully fixed in newer cairo versions. I can't reproduce the bugs and no one else seems to have this problem. Closing the bug now.