<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: WebGL graphics memory stealing issue</title>
	<atom:link href="http://blog.mozilla.org/security/2011/06/16/webgl-graphics-memory-stealing-issue/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.org/security/2011/06/16/webgl-graphics-memory-stealing-issue/</link>
	<description></description>
	<lastBuildDate>Wed, 19 Jun 2013 20:46:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Dan</title>
		<link>http://blog.mozilla.org/security/2011/06/16/webgl-graphics-memory-stealing-issue/comment-page-1/#comment-109739</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Tue, 21 Jun 2011 16:51:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/security/?p=485#comment-109739</guid>
		<description><![CDATA[Which bug numbers fixed this for Firefox 5?]]></description>
		<content:encoded><![CDATA[<p>Which bug numbers fixed this for Firefox 5?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Veditz</title>
		<link>http://blog.mozilla.org/security/2011/06/16/webgl-graphics-memory-stealing-issue/comment-page-1/#comment-109736</link>
		<dc:creator>Daniel Veditz</dc:creator>
		<pubDate>Sat, 18 Jun 2011 21:28:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/security/?p=485#comment-109736</guid>
		<description><![CDATA[Phil: this has nothing to do with your crashes which are almost certainly due to incompatible 3rd party software. If you&#039;ve submitted crash reports to Mozilla and know the crash IDs we might be able to finger the culprit. Some problems are solved by starting in &quot;safe-mode&quot; and then disabling the bad add-on or plugin. If safe-mode doesn&#039;t help sometimes the problem is a malware infection that has gone unnoticed until it starts conflicting with things--in which case switching to IE may stop the crashing but you&#039;ve still got the malware spying on you!

There are too many possibilities to diagnose in a blog, please seek help from http://support.mozilla.com/]]></description>
		<content:encoded><![CDATA[<p>Phil: this has nothing to do with your crashes which are almost certainly due to incompatible 3rd party software. If you&#8217;ve submitted crash reports to Mozilla and know the crash IDs we might be able to finger the culprit. Some problems are solved by starting in &#8220;safe-mode&#8221; and then disabling the bad add-on or plugin. If safe-mode doesn&#8217;t help sometimes the problem is a malware infection that has gone unnoticed until it starts conflicting with things&#8211;in which case switching to IE may stop the crashing but you&#8217;ve still got the malware spying on you!</p>
<p>There are too many possibilities to diagnose in a blog, please seek help from <a href="http://support.mozilla.com/" rel="nofollow">http://support.mozilla.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil</title>
		<link>http://blog.mozilla.org/security/2011/06/16/webgl-graphics-memory-stealing-issue/comment-page-1/#comment-109734</link>
		<dc:creator>Phil</dc:creator>
		<pubDate>Sat, 18 Jun 2011 17:15:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/security/?p=485#comment-109734</guid>
		<description><![CDATA[Could this be why my machine crashes, if I try to update from 3.6 to 4?  I don&#039;t have a video card, just the onboard &amp; non-3D video.  It&#039;s not just FF freezing, the entire OS crashes on first run of FF 4! I had to use IE to research how to roll back.  Until I know exactly what it is, this machine will never run FF 4.  My secondary PC made the transition OK, however.]]></description>
		<content:encoded><![CDATA[<p>Could this be why my machine crashes, if I try to update from 3.6 to 4?  I don&#8217;t have a video card, just the onboard &amp; non-3D video.  It&#8217;s not just FF freezing, the entire OS crashes on first run of FF 4! I had to use IE to research how to roll back.  Until I know exactly what it is, this machine will never run FF 4.  My secondary PC made the transition OK, however.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anonmouse</title>
		<link>http://blog.mozilla.org/security/2011/06/16/webgl-graphics-memory-stealing-issue/comment-page-1/#comment-109733</link>
		<dc:creator>anonmouse</dc:creator>
		<pubDate>Fri, 17 Jun 2011 22:04:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/security/?p=485#comment-109733</guid>
		<description><![CDATA[In general, WHY is webGL enabled by default on all sites? This seems like a very dumb decision security wise. The spec is nascent right now, why not have a pop up saying &quot;Do you want to enable this beta feature for this site for now?&quot; ?]]></description>
		<content:encoded><![CDATA[<p>In general, WHY is webGL enabled by default on all sites? This seems like a very dumb decision security wise. The spec is nascent right now, why not have a pop up saying &#8220;Do you want to enable this beta feature for this site for now?&#8221; ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Veditz</title>
		<link>http://blog.mozilla.org/security/2011/06/16/webgl-graphics-memory-stealing-issue/comment-page-1/#comment-109732</link>
		<dc:creator>Daniel Veditz</dc:creator>
		<pubDate>Fri, 17 Jun 2011 15:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/security/?p=485#comment-109732</guid>
		<description><![CDATA[Firefox 5 -is- the Firefox 4 refesh

http://www.conceivablytech.com/7747/products/no-more-updates-for-firefox-4-chromium-14-released (also see earlier &quot;lifecycle&quot; thread on mozilla.dev.planning)

From a product perspective there will be no more &quot;Firefox N&quot;, just &quot;Firefox&quot;. The number is there under the hood so people can double-check they&#039;re up to date.]]></description>
		<content:encoded><![CDATA[<p>Firefox 5 -is- the Firefox 4 refesh</p>
<p><a href="http://www.conceivablytech.com/7747/products/no-more-updates-for-firefox-4-chromium-14-released" rel="nofollow">http://www.conceivablytech.com/7747/products/no-more-updates-for-firefox-4-chromium-14-released</a> (also see earlier &#8220;lifecycle&#8221; thread on mozilla.dev.planning)</p>
<p>From a product perspective there will be no more &#8220;Firefox N&#8221;, just &#8220;Firefox&#8221;. The number is there under the hood so people can double-check they&#8217;re up to date.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Kaply</title>
		<link>http://blog.mozilla.org/security/2011/06/16/webgl-graphics-memory-stealing-issue/comment-page-1/#comment-109731</link>
		<dc:creator>Michael Kaply</dc:creator>
		<pubDate>Fri, 17 Jun 2011 13:42:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/security/?p=485#comment-109731</guid>
		<description><![CDATA[So this bug will only be fixed in Firefox 5? There are no plans to put this in a Firefox 4 refresh?]]></description>
		<content:encoded><![CDATA[<p>So this bug will only be fixed in Firefox 5? There are no plans to put this in a Firefox 4 refresh?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny Moules</title>
		<link>http://blog.mozilla.org/security/2011/06/16/webgl-graphics-memory-stealing-issue/comment-page-1/#comment-109730</link>
		<dc:creator>Danny Moules</dc:creator>
		<pubDate>Fri, 17 Jun 2011 09:16:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/security/?p=485#comment-109730</guid>
		<description><![CDATA[Good catch, though the value of the actual abstract they&#039;ve provided to the public leaves much to be desired (it&#039;s called ARB_robustness, not ARB_watertight). It&#039;s nice to see people are putting WebGL implementations through their well-needed paces.]]></description>
		<content:encoded><![CDATA[<p>Good catch, though the value of the actual abstract they&#8217;ve provided to the public leaves much to be desired (it&#8217;s called ARB_robustness, not ARB_watertight). It&#8217;s nice to see people are putting WebGL implementations through their well-needed paces.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed</title>
		<link>http://blog.mozilla.org/security/2011/06/16/webgl-graphics-memory-stealing-issue/comment-page-1/#comment-109729</link>
		<dc:creator>Ed</dc:creator>
		<pubDate>Fri, 17 Jun 2011 06:03:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/security/?p=485#comment-109729</guid>
		<description><![CDATA[Worlds of Worry!
context? OK MS bs OK just know it.
Move on!]]></description>
		<content:encoded><![CDATA[<p>Worlds of Worry!<br />
context? OK MS bs OK just know it.<br />
Move on!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
