<?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: Cycle collector landing</title>
	<atom:link href="http://blog.mozilla.com/graydon/2006/11/21/cycle-collector-landing/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.com/graydon/2006/11/21/cycle-collector-landing/</link>
	<description>some unappealing details</description>
	<lastBuildDate>Thu, 21 Jun 2007 14:24:03 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Firefox XPCOM ciklu savācējs ēdīs atmiņu &#187; Latvijas interneta pods</title>
		<link>http://blog.mozilla.com/graydon/2006/11/21/cycle-collector-landing/comment-page-1/#comment-135</link>
		<dc:creator>Firefox XPCOM ciklu savācējs ēdīs atmiņu &#187; Latvijas interneta pods</dc:creator>
		<pubDate>Sat, 10 Mar 2007 22:24:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/graydon/2006/11/21/cycle-collector-landing/#comment-135</guid>
		<description>[...] 11.janvāra Firefox stumbra (trunk) versijā esot ielikts XPCOM ciklu savācējs. In general, unfortunately, you should expect this patch to cause the browser to use somewhat more memory and somewhat more CPU time than before the patch lands. It is not a panacea. The purpose of the patch is only to provide infrastructure for simpler ownership rules. Rather than try to reason about which pointer ought to own which other pointer inside gecko, and which pointers are safe to consider weak or raw, you now get a simple and universal rule. [...]</description>
		<content:encoded><![CDATA[<p>[...] 11.janvāra Firefox stumbra (trunk) versijā esot ielikts XPCOM ciklu savācējs. In general, unfortunately, you should expect this patch to cause the browser to use somewhat more memory and somewhat more CPU time than before the patch lands. It is not a panacea. The purpose of the patch is only to provide infrastructure for simpler ownership rules. Rather than try to reason about which pointer ought to own which other pointer inside gecko, and which pointers are safe to consider weak or raw, you now get a simple and universal rule. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
