I'm not really sure what is causing this but in the current stable version of safari on OSX 10.7.X I'm only seeing 3-4 frames rendered. I downloaded the lastest safari beta and it seems like they improved it, but its still dropping a large amount of frames.
Here is an demo that should be viewed in Safari on Lion:
http://jsfiddle.net/JEKAh/1/
Please respond if you know why or what is going on
edit: still is a problem on mountain lion
It turns out that this bug is related to the transfer encoding of the video files. If you are sending the video with Content-Ranges you will see this issue in safari. But if you send the video using Transfer-Encoding: chunked... it will work fine
I used a simple node server to test this: https://gist.github.com/3746561/c303f84866542c4a6ec2956ecf158cb9f492a7a2
-- edit
the above is only a fix for Lion, it appears that Safari Mountain Lion is unable to render frames from a video that is sent using a chunked transfer encoding, a side affect of this is also massive safari memory leaks... I ran a video being piped for canvas for 2 mins and the Safari Web Content process shot up to 12GB of real mem used. -_-
-- edit
after additional research i have found the original issue with standard video to canvas in a recent nightly webkit 537.3 and have confirmed that currently in webkit 537.11 these issues no longer exist... so all i can do is hope that apple updates safari soon including the webkit fixes
-- edit
this is now fixed in OSX 10.9 :)
Firstly, I acknowledge that this might not be the answer you are looking for but it's something which I've just been dealing with for a client so I thought I'd throw it up here:
They reported that their site "Was no longer working well and the animation was jumpy".. (hmm..) Their site uses canvas rendered videos with some overlays for a lot of the visual elements.
So after a while we determined that they had just updated their MacBook Pro to Lion and now their site was slower and less responsive. I was a bit baffled so I got them to bring it to me. To cut to the chase:
Lion & Mountain Lion require a tonne more physical memory (RAM) than Snow Leopard did (due to the new VM architecture as I understand it), I compared their site playback to another MBP with a lower spec, with SL installed and the SL version ran smoother.
After a bit of reading on the Apple support forums which suggested adding RAM, it was all fine again, in fact it seemed smoother than ever..
Not really a programatical answer but one which I thought may be relevant..
Related
I'm facing a really weird issue on Chrome 62/63, only on MacOS (el capitan and sierra at least).
I have a big sprite (14400 * 4400), that is used inside a HTML5 canvas, and the animation that I do, is really really slow on this platform. I tried on Windows (this browser version and IE/Edge), no problem, and on a lot of other browser (opera neon, vivaldi, firefox, safari), there's no problem. Even on chrome 61 and before, there's no problem. It's only working when I activate the flag "Accelerated 2D canvas" on chrome 62+
I know, that the sprite is huge, its size is already divided by 2 (28800*8800 is the initial size), so is there any way to improve the performances via canvas config or something else ? (I already read this article), I almost follow everything from this article, except the "requestAnimationFrame", because I need to do the job at a certain time. (I don't know if it's a chrome bug or just me doing the wrong thing, but I have no more idea)
I discovered I had a problem when I checked one of my uploaded three.js projects. At first I thought maybe I had done something wrong. My project used r63, so I updated to r65, but that didn't solve the problem, even after clearing the cache and refreshing. I then checked a couple of the demos from the three.js site, and I found they are slow for me, too. As an example, http://carvisualizer.plus360degrees.com/threejs/ autorotates incredibly slowly in Chrome, but at normal speed in Firefox and IE 11. I also tried http://helloracer.com/webgl/ which is fine in Firefox but really choppy in Chrome. It's a disaster in IE11, by the way, but it's an older demo. My project uses OrbitControls, with autorotate enabled. The model is a 16MB JSON file (200,000 triangles), but it worked fine before and works fine in Firefox and IE11. I'm on a Windows 7 machine with a GTX Titan (work computer). Thanks!
type chrome://flags in chrome address bar, and look for settings #ignore-gpu-blacklist
this happened to me, suddenly my gpu was added to blacklist and chrome reverted to software rendering..
For me running google-chrome on linux I needed to enable Use hardware acceleration when available in chrome://settings
I'm trying to understand these strange rendering error boxes that are too big to be ignored. This seems to happen on Chrome in Windows 7 (my testing isn't too elaborate) and nowhere else. When I attempt to inspect, they all disappear. This could be some kind of video card issue as I'm using some pretty advanced CSS3 transitions that could mess up memory. In any case, if someone could offer advice on what I could do to fix, I'm at a loss. The site is www.crane-usa.com
Having the same issue with our site using 21.0.1180.89 and 21.0.1180.79. Problem is in Windows 7, Mac OS X latest, Ubuntu and in Chrome frame running in IE9. IE9 with Chrome frame disabled works fine. The problems are intermittent and unrepeatable. Inspect element removes the problem as you say. I tried disabling GPU compositing via chrome://flags but that didn't fix the issue.
We and our users have only been seeing these issues since approx Aug 27, 2012, 3 days ago. I took a look in crbugs.com and found that this seems to have existed for a couple of weeks already. http://code.google.com/p/chromium/issues/detail?id=143647
Sorry our site is not public so I can't post our url but you're not alone.
Just updated Chrome to 18.0.1025.142 from 17 on a Mac running 10.7.1 and it's killed the performance of our site. We've been using translate3d where available to move a large number of items around the screen. I'm animating with requestAnimationFrame. In 17 we were getting framerates upwards of 50fps. Now lucky to get 15fps. It's really bad.
Has hardware acceleration been turned off by default? Anyone else noticed any problems like this? I've noticed the font rendering has been improved and is now on a par with Safari (which runs the site beautifully) maybe this change has had an effect on general rendering performance?
I'm afraid I can't share the link due to an NDA. But any help would be greatly appreciated!
Update:
As far as I can tell it IS still GPU accelerated but the performance is really bad, other people have reported similar things. The Chromium builds of v19 seem to be back to the old quality of performance.
There used to be a flag when launching chrome --show-composited-layer-borders which would put red borders around gpu accelerated elements. This option now seems to have been added to chrome://flags/ but it paints green borders around layers and doesn't seem to distinguish gpu elements any more. Does anyone know of an option to show if elements are being rendered by the gpu?
chrome://gpu/ says that everything is being hardware accelerated...
Reproduce the problem with fresh code in a new web page. This will greatly help both your SO question and bug report.
Browsers regularly tweak whether hardware acceleration is used based on whether your graphics card and driver version is supported. Updating your graphics card driver may fix the problem for you, but maybe not everyone else. (This tool I wrote might help: graphics driver updater)
In fact it's a bad idea for your website to depend on hardware acceleration, because a significant fraction of users have crappy unsupported hardware and/or out of date drivers which are blacklisted to stop the user's computer crashing while they browse the web. They'll get crappy, un-accelerated framerates too, in any version of Chrome.
So IMO the real problem is your website depends on hardware acceleration which not everyone has, and you just noticed because Google blacklisted your setup in Chrome 18.
I'm posting this question here, but I'm not 100% sure where the problem lies. I have a site hosted through Media Temple that I'm developing. It's started to continually give me http 206 responses (partial content) on image and js assets. I see these through firebug. This results in missing images and js files, or in some browsers like Safari, half rendered images. When I view my work off my local server I see no issues.
I see this behavior on all browsers, firefox 3.6, safari 5.0.3, chrome 8. I work off of mac os x 10.6.6. Different images exhibit this behavior at different times, and the only thing that works temporarily is to clear the cache, but I'll typically begin to see the problem again shortly.
The other thing, as much as I can tell, I don't see this problem on other machines. My work machine (also a Mac) doesn't show this behavior at all. The clients this site is for have never complained of these issues at all.
I've also taken some of these problematic assets and moved them to other servers and pointed my browser there, no problem, so it doesn't seem to be a corrupt file.
I've run out of places to look and was hoping someone on these forums might have some suggestions. This is a real mystery and would love to get to the bottom of it.
Sounds like a problem on the server side. Have you tried restarting the web server or taking a look at the error log?