Earlier quoted context omitted.
Only thing I can think of at this point is that you have an extension inserting something into the body before the canvas. While on Magister, drop javascript:alert(document.body.firstChild) into the address bar and see if you get the canvas -- if not, that's the problem.
The tab crashes after a while when I try that. Weird. Even with all extensions disabled, it hangs without ever finishing loading.
Show HN: My first WebGL demo, the first self-extracting PNG ever?
31–40 of 56 posts
Re: Show HN: My first WebGL demo, the first self-extracting PNG ever?
#32Earlier quoted context omitted.
It's fairly GPU intensive, and if Windows Vista/7 don't get a response from the GPU after a short period of time, it'll restart the drivers. Happens every once in a while even on newer GPUs, unfortunately.
Ah. So your interpretation is not that the driver actually crashed, but that it simply was overwhelmed by the workload, and didn't respond properly within the timeout limit as set by the OS?
Re: Show HN: My first WebGL demo, the first self-extracting PNG ever?
#33Earlier quoted context omitted.
Pretty cool hack! I'm looking forward to the blog post. It doesn't seem to eat my processor too much. In Chrome with AMD processor it's sitting at about 25% CPU usage.
Thanks! It isn't too be on the CPU for most people, but for some reason it's eating a massive chunk of CPU-time for some people -- seems to be only in the latest Firefox nightlies, but i'm not seeing it here, so I'm unsure of what it could be.
Re: Show HN: My first WebGL demo, the first self-extracting PNG ever?
#34Earlier quoted context omitted.
The tab crashes after a while when I try that. Weird. Even with all extensions disabled, it hangs without ever finishing loading.
Old version of chrome perhaps? Works fine on my chrome on osx here. 12.0.742.122 here. (I'm technically out of date too, mostly because I haven't restarted chrome in a while)
Re: Show HN: My first WebGL demo, the first self-extracting PNG ever?
#35So, it the header makes it look like a PNG: magister.html: PNG image data, 1242 x 1, 8-bit grayscale, non-interlaced If you look at this in an image viewer, it's as advertised: a long black bar. So what this is is some garbage data with a PNG header, a token PNG image, and some HTML that bootstraps a javascript program whose main body looks like binary garbage. But it's not a self-extracting PNG, it's a very strange…
Re: Show HN: My first WebGL demo, the first self-extracting PNG ever?
#36Earlier quoted context omitted.
I cannot, although all of the demos I've tried here work: http://www.khronos.org/webgl/wiki/Demo_Repository
Only thing I can think of at this point is that you have an extension inserting something into the body before the canvas. While on Magister, drop javascript:alert(document.body.firstChild) into the address bar and see if you get the canvas -- if not, that's the problem.
Though interestingly, the behavior in all three Chromes is wildly different: Dev runs 60% CPU use in the rendering process, Beta sometimes uses nothing, sometimes 60%, and Stable uses the same 60% + 120% on "google chrome helper". The alert test works (shows a canvas element) in both Dev and Beta, Stable shows me a "page unresponsive" after a couple seconds and never alerts anything.
Other GL tests work just fine in all 3. I'll be happy to test other things if you can come up with them :)
Re: Show HN: My first WebGL demo, the first self-extracting PNG ever?
#37Re: Show HN: My first WebGL demo, the first self-extracting PNG ever?
#38Earlier quoted context omitted.
Do you have a quad core CPU by chance? 25% is the max that a single-threaded process would use. (Someone please correct me if this is wrong, but at least this is the behavior I've observed.) That being said, this uses only 10-12% CPU on my quad-core machine.
It depends on what you use to report CPU usage. Many monitoring tools stick with 100%/core, but some normalize it.
Re: Show HN: My first WebGL demo, the first self-extracting PNG ever?
#39Apologies, but nothing happens when I view it. Running Chrome 12.0.742.122. I see the initial raw PNG splat, but get nothing but a lot of high cpu and a blank browser screen after running a couple minutes.
Re: Show HN: My first WebGL demo, the first self-extracting PNG ever?
#40Apologies, but nothing happens when I view it. Running Chrome 12.0.742.122. I see the initial raw PNG splat, but get nothing but a lot of high cpu and a blank browser screen after running a couple minutes.
For what its worth, it seems to be running now without any changes on my part.