threejs is having some serious issues with some polygons
I'm on their site, viewing their examples.
On my computer, It starts out fine, like the first image below, but within a few seconds, becomes the mess in the second part of that image.
you can see that it works in your browser here
I've tried clearing my history, cache, cookies, anything I can think of. I've even switched Firefox from Chrome. nothing seems to work.
any ideas? is this a webgl issue?
This appears to be an AMD Catalyst driver issue. I uninstalled it and the issue was resolved. It's now using the default drivers. I'll update if I ever install new drivers, but for now I'm leaving it as is.
Related
Recently a Chrome extension our company uses was reported to be causing extreme slow down in the UI when in use. Ive been trying to find the cause of this issue.
After a week or two I have narrowed it down to the canvas's drawImage method.
Initial thought was that this method was holding onto the thread for too long.
This extension works great up to Chrome V43 (couldn't find chrome V44 anyway). With the current version 45, it causes heavy delay on UI response. Seems like a chrome bug.
Googling around I found this https://code.google.com/p/chromium/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified&groupby=&sort=&id=490478
I am not sure if this is exactly the issue I am running into with drawImage but taking the suggestion from someone who posted there, I went into chrome://flags/ and disabled "Disable accelerated 2D canvas".
This instantly solved the issue & the extension is actually working better than ever before. The question is why? and how can this be used to make a temporary fix to the code since it'd be unreasonable to just ask everyone to disable this flag.
I'm a bit confused because my project worked yesterday but seems to no longer work correctly today. (Yes, I've checked previous versions from git.)
The problem: Some divs previously hidden with -webkit-backface-visibility: hidden; magically appeared.
I have isolated this issue into a fiddle:
http://jsfiddle.net/Js6cg/1/
The div is visible in Chrome at 23.0.1271.64 m (wrong) but hidden in 25.0.1326.0 canary (as I expected).
Can you confirm that this is indeed a bug in Chrome or am I using the CSS incorrectly somehow?
(I've updated my GPU drivers (AMD Catalyst) from 12.8 to 12.10 today, if that's important.)
Additionally, the site that demonstrates the effect I've been reproducing appears to work +- correctly at Chrome stable (except for aparrently ignoring -webkit-perspective and animating kind of choppy), while Chrome canary renders it very well and accepts the perspective. I'm confused.
OK, that is embarassing.
The story looks like: I've updated the GPU drivers but looks like I haven't actually restarted Chrome for ages. For some reason, it was unable to re-enable GPU compositing after the driver update and hence some more advanced CSS3 effects (like perspective and backface-visibility) didn't work at all, while simple transforms used a fallback CPU implementation, which also made them look choppy and on the demo site.
I've started Chrome Canary well after the driver update, so it didn't have any issues with GPU compositing. One instance worked, another didn't, but version mismatch wasn't important here at all.
Restarting Chrome fixed that issue. And I'm taking a break!
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.
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?
I have a big problem with my web site (you can see here), several user can't see images with firefox. I use too firefox but I don't have this problem.
These users use firefox 3.5.2 with windows XP or VISTA. I have no idea to find the problem.
Have you any idea ?
Thanks a lot.
Perhaps the user has accidentally blocked images from your domain.
In Firefox:
Tools > Options > Content tab > Load images automatically should be checked > click Exceptions... make sure the Site list does not include mowen-world.com. If it is there, highlight it and click Remove Site.
I've had similar issues a few weeks ago. The reason was that the JPG images were somehow corrupted. Some browsers/OS combinations showed them without problems, but on others they didn't show.
I fixed it by opening every JPG image and saving them again in a good image editor (like Photoshop or Fireworks)
Whenever I get a problem like this, I start from basics... like "is the HTML valid".
http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fmorwen-world.com%2F
There are some issues listed here that could cause odd behaviour.
When I look at the site, I can see all the images fine and the website looks reasonably well laid out (Firefox 3.0.14 Windows XP AND Internet Explorer 8 Windows XP).
I can't see an issue using Firefox 3.5.3 on Windows Vista, just FYI.
Personally whenever I have issues with assets not loading or markup/CSS behaving weirdly, my first stop is Firebug. The Net panel shows the requests for any images and their respective responses. Certainly a good place to start looking.