<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/marks/search/leaks">
<title>Public marks with search leaks</title>
<description>Public marks with search leaks</description>
<link>http://blogmarks.net/marks/search/leaks</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/alamat/mark/1058473053"/>
<rdf:li resource="http://blogmarks.net/api/user/vrossign/mark/1058469738"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058455471"/>
<rdf:li resource="http://blogmarks.net/api/user/jey/mark/1058544894"/>
<rdf:li resource="http://blogmarks.net/api/user/eaque/mark/1058042746"/>
<rdf:li resource="http://blogmarks.net/api/user/greut/mark/1057671010"/>
<rdf:li resource="http://blogmarks.net/api/user/ERSWeb/mark/1057638511"/>
<rdf:li resource="http://blogmarks.net/api/user/jey/mark/1058546175"/>
<rdf:li resource="http://blogmarks.net/api/user/BlueVoodoo/mark/1057390045"/>
<rdf:li resource="http://blogmarks.net/api/user/zedix/mark/1057387983"/>
<rdf:li resource="http://blogmarks.net/api/user/decembre/mark/2566988"/>
<rdf:li resource="http://blogmarks.net/api/user/BlueVoodoo/mark/1361958"/>
<rdf:li resource="http://blogmarks.net/api/user/mapleelpam/mark/1355587"/>
<rdf:li resource="http://blogmarks.net/api/user/zedix/mark/1057388384"/>
<rdf:li resource="http://blogmarks.net/api/user/fakechris/mark/1251326"/>
<rdf:li resource="http://blogmarks.net/api/user/marco/mark/1041639"/>
<rdf:li resource="http://blogmarks.net/api/user/chris96321/mark/452648"/>
<rdf:li resource="http://blogmarks.net/api/user/fakechris/mark/1253658"/>
<rdf:li resource="http://blogmarks.net/api/user/wyliej/mark/375751"/>
<rdf:li resource="http://blogmarks.net/api/user/micah/mark/332346"/>
<rdf:li resource="http://blogmarks.net/api/user/bader/mark/287940"/>
<rdf:li resource="http://blogmarks.net/api/user/YukuanMark/mark/269489"/>
<rdf:li resource="http://blogmarks.net/api/user/YukuanMarks/mark/268612"/>
<rdf:li resource="http://blogmarks.net/api/user/Riduidel/mark/171641"/>
<rdf:li resource="http://blogmarks.net/api/user/multilinko/mark/135901"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/alamat/mark/1058473053">
<title>Eric Dane, Rebecca Gayheart threesome nude video leaks: Gray anatomy?  </title>
<link>http://pinoymeetsworld.com/eric-dane-rebecca-gayheart-threesome-nude-video-leaks-gray-anatomy/</link>
<description>A tape of who appears to be “Grey’s Anatomy” star Eric Dane, his wife Rebecca Gayheart, and another woman — reportedly former Miss United States Teen Kari Ann Peniche — together in a nude video has spread online, but a lawyer for the couple said the tape should “not be used for any commercial purposes.”  </description>
<dc:date>2009-08-19T18:59:38Z</dc:date>
<dc:author>alamat</dc:author>
<dc:subject>nude, video, scandal, leaks</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://pinoymeetsworld.com/eric-dane-rebecca-gayheart-threesome-nude-video-leaks-gray-anatomy/"><img border="0" src="http://blogmarks.net/screenshots/2009/08/19/0ebcdb0026ab1859a1ec7db206c9040c.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://pinoymeetsworld.com/eric-dane-rebecca-gayheart-threesome-nude-video-leaks-gray-anatomy/">Eric Dane, Rebecca Gayheart threesome nude video leaks: Gray anatomy?  </a></h4>
 
by <a href="http://blogmarks.net/user/alamat">alamat</a> 
<p class="description">A tape of who appears to be “Grey’s Anatomy” star Eric Dane, his wife Rebecca Gayheart, and another woman — reportedly former Miss United States Teen Kari Ann Peniche — together in a nude video has spread online, but a lawyer for the couple said the tape should “not be used for any commercial purposes.”  </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/nude">nude</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/video">video</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/scandal">scandal</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/leaks">leaks</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058473053">Copy</a> | 
<a href="http://blogmarks.net/link/3320129">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/vrossign/mark/1058469738">
<title>perfection kills » Blog Archive » Detecting global variable leaks</title>
<link>http://thinkweb2.com/projects/prototype/detecting-global-variable-leaks/</link>
<description></description>
<dc:date>2009-08-17T09:03:17Z</dc:date>
<dc:author>vrossign</dc:author>
<dc:subject>bookmarklet, global, js, security, leaks, Analyze</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://thinkweb2.com/projects/prototype/detecting-global-variable-leaks/"><img border="0" src="http://blogmarks.net/screenshots/2009/08/17/d6b485043a0b65da38032acaa069a8db.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://thinkweb2.com/projects/prototype/detecting-global-variable-leaks/">perfection kills » Blog Archive » Detecting global variable leaks</a></h4>
 
by <a href="http://blogmarks.net/user/vrossign">vrossign</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bookmarklet">bookmarklet</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/global">global</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/js">js</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/security">security</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/leaks">leaks</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Analyze">Analyze</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058469738">Copy</a> | 
<a href="http://blogmarks.net/link/3317303">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058455471">
<title>S.Lott-Software Architect: Privacy and Encryption</title>
<link>http://slott-softwarearchitect.blogspot.com/2009/07/privacy-and-encryption.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;Without an applicable encryption standard -- and some boundaries on what's really required -- I think these legal initiatives will do more harm than good. To prevent the various risks, companies will do dumb things. Things that are probably dumber than what they've done that lead to leaks of personal information.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-08-05T12:42:41Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>securité, opacité</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://slott-softwarearchitect.blogspot.com/2009/07/privacy-and-encryption.html"><img border="0" src="http://blogmarks.net/screenshots/2009/08/05/086568f14b370777d765788ddd896e6d.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://slott-softwarearchitect.blogspot.com/2009/07/privacy-and-encryption.html">S.Lott-Software Architect: Privacy and Encryption</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>Without an applicable encryption standard -- and some boundaries on what's really required -- I think these legal initiatives will do more harm than good. To prevent the various risks, companies will do dumb things. Things that are probably dumber than what they've done that lead to leaks of personal information.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/securit%25C3%25A9">securité</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/opacit%25C3%25A9">opacité</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058455471">Copy</a> | 
<a href="http://blogmarks.net/link/3306827">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/jey/mark/1058544894">
<title>Memory Analyzer News » Blog Archive » Immortal Objects - Or: How to Find Memory Leaks</title>
<link>http://dev.eclipse.org/blogs/memoryanalyzer/2008/04/21/immortal-objects-or-how-to-find-memory-leaks/</link>
<description></description>
<dc:date>2009-06-02T13:51:44Z</dc:date>
<dc:author>jey</dc:author>
<dc:subject>java, diagnostics, GarbageCollection, memorymanagement</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://dev.eclipse.org/blogs/memoryanalyzer/2008/04/21/immortal-objects-or-how-to-find-memory-leaks/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://dev.eclipse.org/blogs/memoryanalyzer/2008/04/21/immortal-objects-or-how-to-find-memory-leaks/">Memory Analyzer News » Blog Archive » Immortal Objects - Or: How to Find Memory Leaks</a></h4>
 
by <a href="http://blogmarks.net/user/jey">jey</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/java">java</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/diagnostics">diagnostics</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/GarbageCollection">GarbageCollection</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/memorymanagement">memorymanagement</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058544894">Copy</a> | 
<a href="http://blogmarks.net/link/3379124">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/eaque/mark/1058042746">
<title>What's new in PHP V5.2, Part 1: Using the new memory manager</title>
<link>http://www.ibm.com/developerworks/opensource/library/os-php-v521/?ca=dgr-btw15PHP5.2-Memory</link>
<description>nice explainations about memory allocation and some tips about php configuration in order to limit leaks or improve performances</description>
<dc:date>2008-10-30T15:06:15Z</dc:date>
<dc:author>eaque</dc:author>
<dc:subject>programmation, mémoire, php</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.ibm.com/developerworks/opensource/library/os-php-v521/?ca=dgr-btw15PHP5.2-Memory"><img border="0" src="http://blogmarks.net/screenshots/2008/10/30/cb898f65978d26c436765d1eee69ce82.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.ibm.com/developerworks/opensource/library/os-php-v521/?ca=dgr-btw15PHP5.2-Memory">What's new in PHP V5.2, Part 1: Using the new memory manager</a></h4>
 
by <a href="http://blogmarks.net/user/eaque">eaque</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/1894426">1 other(s)</a> 
<p class="description">nice explainations about memory allocation and some tips about php configuration in order to limit leaks or improve performances</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/programmation">programmation</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/m%25C3%25A9moire">mémoire</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/php">php</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058042746">Copy</a> | 
<a href="http://blogmarks.net/link/1894426">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/greut/mark/1057671010">
<title>GPDE Team Blog : JavaScript Memory Leak Detector</title>
<link>http://blogs.msdn.com/gpde/pages/javascript-memory-leak-detector.aspx</link>
<description>&lt;blockquote&gt;&lt;p&gt;JavaScript Memory Leak Detector is a debugging tool to detect memory leaks in JavaScript code. It can be installed as an Internet Explorer band and it is expressly designed to find memory leaks in JavaScript code that runs in Internet Explorer.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;&lt;/p&gt;</description>
<dc:date>2008-01-25T15:57:29Z</dc:date>
<dc:author>greut</dc:author>
<dc:subject>javascript, code, tool, msie, leak</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://blogs.msdn.com/gpde/pages/javascript-memory-leak-detector.aspx"><img border="0" src="http://blogmarks.net/screenshots/2008/01/26/4451aa7b6f47c42956be6eb365903708.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://blogs.msdn.com/gpde/pages/javascript-memory-leak-detector.aspx">GPDE Team Blog : JavaScript Memory Leak Detector</a></h4>
 
by <a href="http://blogmarks.net/user/greut">greut</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2646102">1 other(s)</a> 
<div class="description"><blockquote><p>JavaScript Memory Leak Detector is a debugging tool to detect memory leaks in JavaScript code. It can be installed as an Internet Explorer band and it is expressly designed to find memory leaks in JavaScript code that runs in Internet Explorer.</p></blockquote>
<p></p></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/javascript">javascript</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/code">code</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tool">tool</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/msie">msie</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/leak">leak</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057671010">Copy</a> | 
<a href="http://blogmarks.net/link/2646102">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ERSWeb/mark/1057638511">
<title>Code profiling, memory profiling, .NET profiler - ANTS Profiler</title>
<link>http://www.red-gate.com/products/ants_profiler/index.htm</link>
<description>Identify performance bottlenecks quickly and easily 
Optimize memory usage and locate memory leaks 
Visual Studio integration with context sensitivity 
Download file includes FREE PInvoke.net Visual Studio Add-in </description>
<dc:date>2008-01-03T20:17:44Z</dc:date>
<dc:author>ERSWeb</dc:author>
<dc:subject>.net, performance, code, development</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.red-gate.com/products/ants_profiler/index.htm"><img border="0" src="http://blogmarks.net/screenshots/2008/01/03/f601f54a983896d4935761895463058d.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.red-gate.com/products/ants_profiler/index.htm">Code profiling, memory profiling, .NET profiler - ANTS Profiler</a></h4>
 
by <a href="http://blogmarks.net/user/ERSWeb">ERSWeb</a> 
<p class="description">Identify performance bottlenecks quickly and easily 
Optimize memory usage and locate memory leaks 
Visual Studio integration with context sensitivity 
Download file includes FREE PInvoke.net Visual Studio Add-in </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/.net">.net</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/performance">performance</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/code">code</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/development">development</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057638511">Copy</a> | 
<a href="http://blogmarks.net/link/2618095">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/jey/mark/1058546175">
<title>Rich-client application performance, Part 2: Plugging memory leaks</title>
<link>http://www.ibm.com/developerworks/java/library/j-rcp2/</link>
<description></description>
<dc:date>2007-10-08T17:18:41Z</dc:date>
<dc:author>jey</dc:author>
<dc:subject>performance, eclipse, profiling, MemoryAnalysis</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.ibm.com/developerworks/java/library/j-rcp2/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.ibm.com/developerworks/java/library/j-rcp2/">Rich-client application performance, Part 2: Plugging memory leaks</a></h4>
 
by <a href="http://blogmarks.net/user/jey">jey</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/performance">performance</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/eclipse">eclipse</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/profiling">profiling</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/MemoryAnalysis">MemoryAnalysis</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058546175">Copy</a> | 
<a href="http://blogmarks.net/link/3380189">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/BlueVoodoo/mark/1057390045">
<title>Rich-Client app performance, Pt 2: Plugging Leaks</title>
<link>http://www.ibm.com/developerworks/java/library/j-rcp2/index.html?ca=dgr-btw15rcpp2mem&amp;S_TACT=105AGX59&amp;S_CMP=HP</link>
<description>Part 1 of this two-part article on Eclipse rich-client performance covers the basics of measuring an application's performance, applying instrumentation techniques, keeping the UI responsive, and using Jobs to avoid threading mistakes. This second part takes a look at memory usage and how to chase down memory leaks.</description>
<dc:date>2007-08-07T19:43:57Z</dc:date>
<dc:author>BlueVoodoo</dc:author>
<dc:subject>programming, java</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.ibm.com/developerworks/java/library/j-rcp2/index.html?ca=dgr-btw15rcpp2mem&amp;S_TACT=105AGX59&amp;S_CMP=HP"><img border="0" src="http://blogmarks.net/screenshots/2007/08/07/fa80c89137e50dbff6ffed1ad004e55e.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.ibm.com/developerworks/java/library/j-rcp2/index.html?ca=dgr-btw15rcpp2mem&amp;S_TACT=105AGX59&amp;S_CMP=HP">Rich-Client app performance, Pt 2: Plugging Leaks</a></h4>
 
by <a href="http://blogmarks.net/user/BlueVoodoo">BlueVoodoo</a> 
<p class="description">Part 1 of this two-part article on Eclipse rich-client performance covers the basics of measuring an application's performance, applying instrumentation techniques, keeping the UI responsive, and using Jobs to avoid threading mistakes. This second part takes a look at memory usage and how to chase down memory leaks.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/programming">programming</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/java">java</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057390045">Copy</a> | 
<a href="http://blogmarks.net/link/2394886">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/zedix/mark/1057387983">
<title>MSFT Fixes Memory Leaks in IE6 » Clientside</title>
<link>http://clientside.cnet.com/industry-news/msft-fixes-memory-leaks-in-ie6/</link>
<description></description>
<dc:date>2007-06-23T00:55:43Z</dc:date>
<dc:author>zedix</dc:author>
<dc:subject>ie, memory, leaks</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://clientside.cnet.com/industry-news/msft-fixes-memory-leaks-in-ie6/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://clientside.cnet.com/industry-news/msft-fixes-memory-leaks-in-ie6/">MSFT Fixes Memory Leaks in IE6 » Clientside</a></h4>
 
by <a href="http://blogmarks.net/user/zedix">zedix</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ie">ie</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/memory">memory</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/leaks">leaks</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057387983">Copy</a> | 
<a href="http://blogmarks.net/link/2393068">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/decembre/mark/2566988">
<title>Firefox Memory Usage_______PluginDoc:  FQA</title>
<link>http://plugindoc.mozdev.org/faqs/memusage.html</link>
<description>Firefox memory usage has been quite a hot topic since the release of Firefox 1.5. This FQA is designed to provide you with tips on how to minimise the amount of memory Firefox uses, information on what is known to cause memory leaks in Firefox, what is an</description>
<dc:date>2007-02-08T15:59:08Z</dc:date>
<dc:author>decembre</dc:author>
<dc:subject>firefox, cache, extension, howto, tips, troubleshooting, solution, best, officiel, official</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://plugindoc.mozdev.org/faqs/memusage.html"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://plugindoc.mozdev.org/faqs/memusage.html">Firefox Memory Usage_______PluginDoc:  FQA</a></h4>
 
by <a href="http://blogmarks.net/user/decembre">decembre</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/951680">2 other(s)</a> 
<p class="description">Firefox memory usage has been quite a hot topic since the release of Firefox 1.5. This FQA is designed to provide you with tips on how to minimise the amount of memory Firefox uses, information on what is known to cause memory leaks in Firefox, what is an</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/firefox">firefox</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/extension">extension</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/howto">howto</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tips">tips</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/troubleshooting">troubleshooting</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/solution">solution</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/best">best</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/officiel">officiel</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/official">official</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=2566988">Copy</a> | 
<a href="http://blogmarks.net/link/951680">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/BlueVoodoo/mark/1361958">
<title>Isolate and resolve memory leaks using MALLOCDEBUG on AIX Version 5.3</title>
<link>http://www.ibm.com/developerworks/aix/library/au-mallocdebug.html?ca=dgr-btw15MALLOCDEBUG</link>
<description>Memory leaks can be tough and costly problems to solve, so it makes sense to use good tools to clearly point out and understand where the leaks are coming from.  This article outlines an approach you can use while tackling memory leaks, and it discusses how to take advantage of the MALLOCDEBUG tool that is supplied with AIX.</description>
<dc:date>2006-12-12T16:29:50Z</dc:date>
<dc:author>BlueVoodoo</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.ibm.com/developerworks/aix/library/au-mallocdebug.html?ca=dgr-btw15MALLOCDEBUG"><img border="0" src="http://blogmarks.net/screenshots/2006/12/12/2bf48ce71917f602931e544746484ce6.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.ibm.com/developerworks/aix/library/au-mallocdebug.html?ca=dgr-btw15MALLOCDEBUG">Isolate and resolve memory leaks using MALLOCDEBUG on AIX Version 5.3</a></h4>
 
by <a href="http://blogmarks.net/user/BlueVoodoo">BlueVoodoo</a> 
<p class="description">Memory leaks can be tough and costly problems to solve, so it makes sense to use good tools to clearly point out and understand where the leaks are coming from.  This article outlines an approach you can use while tackling memory leaks, and it discusses how to take advantage of the MALLOCDEBUG tool that is supplied with AIX.</p>
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1361958">Copy</a> | 
<a href="http://blogmarks.net/link/1348561">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/mapleelpam/mark/1355587">
<title>測試程式是否有Memory Leaks</title>
<link>http://www.cprogramming.com/debugging/valgrind.html</link>
<description>從ppt上看來的</description>
<dc:date>2006-12-11T11:58:05Z</dc:date>
<dc:author>mapleelpam</dc:author>
<dc:subject>programming, c, memory</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.cprogramming.com/debugging/valgrind.html"><img border="0" src="http://blogmarks.net/screenshots/2006/12/11/2074ffd88d78c6cfb8466b8fcfa53573.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.cprogramming.com/debugging/valgrind.html">測試程式是否有Memory Leaks</a></h4>
 
by <a href="http://blogmarks.net/user/mapleelpam">mapleelpam</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/1122919">1 other(s)</a> 
<p class="description">從ppt上看來的</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/programming">programming</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/c">c</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/memory">memory</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1355587">Copy</a> | 
<a href="http://blogmarks.net/link/1122919">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/zedix/mark/1057388384">
<title>3 Easy Steps to Avoid JavaScript Memory Leaks</title>
<link>http://www.jackslocum.com/yui/2006/10/02/3-easy-steps-to-avoid-javascript-memory-leaks/</link>
<description></description>
<dc:date>2006-10-22T21:22:34Z</dc:date>
<dc:author>zedix</dc:author>
<dc:subject>javascript, memory, leaks</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.jackslocum.com/yui/2006/10/02/3-easy-steps-to-avoid-javascript-memory-leaks/"><img border="0" src="http://blogmarks.net/screenshots/2006/10/03/2c52ccd5f30334eee6da9bb69ef4c175.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.jackslocum.com/yui/2006/10/02/3-easy-steps-to-avoid-javascript-memory-leaks/">3 Easy Steps to Avoid JavaScript Memory Leaks</a></h4>
 
by <a href="http://blogmarks.net/user/zedix">zedix</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/1150116">3 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/javascript">javascript</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/memory">memory</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/leaks">leaks</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057388384">Copy</a> | 
<a href="http://blogmarks.net/link/1150116">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/fakechris/mark/1251326">
<title>Jack Slocum’s Blog » 3 Easy Steps to Avoid JavaScript Memory Leaks</title>
<link>http://www.jackslocum.com/yui/2006/10/02/3-easy-steps-to-avoid-javascript-memory-leaks/</link>
<description></description>
<dc:date>2006-10-07T11:08:56Z</dc:date>
<dc:author>fakechris</dc:author>
<dc:subject>****, javascript</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.jackslocum.com/yui/2006/10/02/3-easy-steps-to-avoid-javascript-memory-leaks/"><img border="0" src="http://blogmarks.net/screenshots/2006/10/03/2c52ccd5f30334eee6da9bb69ef4c175.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.jackslocum.com/yui/2006/10/02/3-easy-steps-to-avoid-javascript-memory-leaks/">Jack Slocum’s Blog » 3 Easy Steps to Avoid JavaScript Memory Leaks</a></h4>
 
by <a href="http://blogmarks.net/user/fakechris">fakechris</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/1150116">3 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/%252A%252A%252A%252A">****</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/javascript">javascript</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1251326">Copy</a> | 
<a href="http://blogmarks.net/link/1150116">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/marco/mark/1041639">
<title>3 Easy Steps to Avoid JavaScript Memory Leaks</title>
<link>http://www.jackslocum.com/yui/2006/10/02/3-easy-steps-to-avoid-javascript-memory-leaks/</link>
<description></description>
<dc:date>2006-10-03T08:20:13Z</dc:date>
<dc:author>marco</dc:author>
<dc:subject>javascript</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.jackslocum.com/yui/2006/10/02/3-easy-steps-to-avoid-javascript-memory-leaks/"><img border="0" src="http://blogmarks.net/screenshots/2006/10/03/2c52ccd5f30334eee6da9bb69ef4c175.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.jackslocum.com/yui/2006/10/02/3-easy-steps-to-avoid-javascript-memory-leaks/">3 Easy Steps to Avoid JavaScript Memory Leaks</a></h4>
 
by <a href="http://blogmarks.net/user/marco">marco</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/1150116">3 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/javascript">javascript</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1041639">Copy</a> | 
<a href="http://blogmarks.net/link/1150116">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/chris96321/mark/452648">
<title>Ajaxian » Screencast on Diagnosing Memory Leaks in IE</title>
<link>http://ajaxian.com/archives/screencast-on-diagnosing-memory-leaks-in-ie</link>
<description></description>
<dc:date>2006-03-31T21:58:31Z</dc:date>
<dc:author>chris96321</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://ajaxian.com/archives/screencast-on-diagnosing-memory-leaks-in-ie"><img border="0" src="http://www.blogmarks.net/screenshots/2006/03/31/f6c3d500d04db2bcd668c12072cc5c36.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://ajaxian.com/archives/screencast-on-diagnosing-memory-leaks-in-ie">Ajaxian » Screencast on Diagnosing Memory Leaks in IE</a></h4>
 
by <a href="http://blogmarks.net/user/chris96321">chris96321</a> 
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=452648">Copy</a> | 
<a href="http://blogmarks.net/link/687363">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/fakechris/mark/1253658">
<title>CodeGuru: Detecting Memory Leaks</title>
<link>http://www.codeguru.com/Cpp/Cpp/cpp_mfc/mem_tracking/article.php/c825/</link>
<description></description>
<dc:date>2006-03-06T07:04:55Z</dc:date>
<dc:author>fakechris</dc:author>
<dc:subject>debugging</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.codeguru.com/Cpp/Cpp/cpp_mfc/mem_tracking/article.php/c825/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.codeguru.com/Cpp/Cpp/cpp_mfc/mem_tracking/article.php/c825/">CodeGuru: Detecting Memory Leaks</a></h4>
 
by <a href="http://blogmarks.net/user/fakechris">fakechris</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/debugging">debugging</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1253658">Copy</a> | 
<a href="http://blogmarks.net/link/1273336">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/wyliej/mark/375751">
<title>Jesse Ruderman » Memory leak detection tool</title>
<link>http://www.squarefree.com/2006/01/13/memory-leak-detection-tool/</link>
<description>David Baron recently wrote a tool that testers can use to help reduce memory leaks in Firefox. With this tool, you can find out what leaks you encounter during your normal browsing patterns and report useful bugs when you encounter leaks.</description>
<dc:date>2006-02-09T03:01:38Z</dc:date>
<dc:author>wyliej</dc:author>
<dc:subject>firefox</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.squarefree.com/2006/01/13/memory-leak-detection-tool/"><img border="0" src="http://www.blogmarks.net/screenshots/2006/02/09/b2e51fd998f23d539b094f700de3b558.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.squarefree.com/2006/01/13/memory-leak-detection-tool/">Jesse Ruderman » Memory leak detection tool</a></h4>
 
by <a href="http://blogmarks.net/user/wyliej">wyliej</a> 
<p class="description">David Baron recently wrote a tool that testers can use to help reduce memory leaks in Firefox. With this tool, you can find out what leaks you encounter during your normal browsing patterns and report useful bugs when you encounter leaks.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/firefox">firefox</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=375751">Copy</a> | 
<a href="http://blogmarks.net/link/566595">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/micah/mark/332346">
<title>Money-Saving Secrets : RealSimple.com</title>
<link>http://www.realsimple.com/realsimple/gallery/print/0,22304,1152145,00.html</link>
<description>20 ways to plug hidden financial leaks — and save up to $3000 a year</description>
<dc:date>2006-02-03T17:03:03Z</dc:date>
<dc:author>micah</dc:author>
<dc:subject>money</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.realsimple.com/realsimple/gallery/print/0,22304,1152145,00.html"><img border="0" src="http://www.blogmarks.net/screenshots/2006/02/03/8f4738803461df15ec3370ac130ac20f.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.realsimple.com/realsimple/gallery/print/0,22304,1152145,00.html">Money-Saving Secrets : RealSimple.com</a></h4>
 
by <a href="http://blogmarks.net/user/micah">micah</a> 
<p class="description">20 ways to plug hidden financial leaks — and save up to $3000 a year</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/money">money</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=332346">Copy</a> | 
<a href="http://blogmarks.net/link/503219">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/bader/mark/287940">
<title>[Mishoo] IE: where's my memory?</title>
<link>http://www.bazon.net/mishoo/articles.epl?art_id=824</link>
<description>Memory leaks in Internet Explorer with javascript explained, and how to avoid them.</description>
<dc:date>2006-01-04T14:12:43Z</dc:date>
<dc:author>bader</dc:author>
<dc:subject>web, javascript, ie, webdev</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.bazon.net/mishoo/articles.epl?art_id=824"><img border="0" src="http://www.blogmarks.net/screenshots/2006/01/04/e716fca95cf38eff2daae81a0586701c.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.bazon.net/mishoo/articles.epl?art_id=824">[Mishoo] IE: where's my memory?</a></h4>
 
by <a href="http://blogmarks.net/user/bader">bader</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/437624">1 other(s)</a> 
<p class="description">Memory leaks in Internet Explorer with javascript explained, and how to avoid them.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/javascript">javascript</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ie">ie</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webdev">webdev</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=287940">Copy</a> | 
<a href="http://blogmarks.net/link/437624">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/YukuanMark/mark/269489">
<title>LeakTracer - trace and analyze memory leaks in C++ programs</title>
<link>http://www.andreasen.org/LeakTracer/</link>
<description></description>
<dc:date>2005-12-18T13:33:34Z</dc:date>
<dc:author>YukuanMark</dc:author>
<dc:subject>tools, computer, software building, c::cpp, profiler::debug</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.andreasen.org/LeakTracer/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.andreasen.org/LeakTracer/">LeakTracer - trace and analyze memory leaks in C++ programs</a></h4>
 
by <a href="http://blogmarks.net/user/YukuanMark">YukuanMark</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/331912">1 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tools">tools</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/computer">computer</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/software%2Bbuilding">software building</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/c%253A%253Acpp">c::cpp</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/profiler%253A%253Adebug">profiler::debug</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=269489">Copy</a> | 
<a href="http://blogmarks.net/link/331912">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/YukuanMarks/mark/268612">
<title>LeakTracer - trace and analyze memory leaks in C++ programs</title>
<link>http://www.andreasen.org/LeakTracer/</link>
<description></description>
<dc:date>2005-12-18T09:22:51Z</dc:date>
<dc:author>YukuanMarks</dc:author>
<dc:subject>tools, computer, software building, c::cpp, profiler::debug</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.andreasen.org/LeakTracer/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.andreasen.org/LeakTracer/">LeakTracer - trace and analyze memory leaks in C++ programs</a></h4>
 
by <a href="http://blogmarks.net/user/YukuanMarks">YukuanMarks</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/331912">1 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tools">tools</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/computer">computer</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/software%2Bbuilding">software building</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/c%253A%253Acpp">c::cpp</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/profiler%253A%253Adebug">profiler::debug</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=268612">Copy</a> | 
<a href="http://blogmarks.net/link/331912">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Riduidel/mark/171641">
<title>Process Explorer</title>
<link>http://www.sysinternals.com/Utilities/ProcessExplorer.html</link>
<description>Ever wondered which program has a particular file or directory open? Now you can find out. Process Explorer shows you information about which handles and DLLs processes have opened or loaded.

The Process Explorer display consists of two sub-windows. The top window always shows a list of the currently active processes, including the names of their owning accounts, whereas the information displayed in the bottom window depends on the mode that Process Explorer is in: if it is in handle mode you’ll see the handles that the process selected in the top window has opened; if Process Explorer is in DLL mode you’ll see the DLLs and memory-mapped files that the process has loaded. Process Explorer also has a powerful search capability that will quickly show you which processes have particular handles opened or DLLs loaded.

The unique capabilities of Process Explorer make it useful for tracking down DLL-version problems or handle leaks, and provide insight into the way Windows and applications work.

Process Explorer works on Windows 9x/Me, Windows NT 4.0, Windows 2000, Windows XP, Server 2003, and 64-bit versions of Windows for x64 processors, and Windows Vista.</description>
<dc:date>2005-10-10T14:31:16Z</dc:date>
<dc:author>Riduidel</dc:author>
<dc:subject>freeware, software, windows, process, system</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.sysinternals.com/Utilities/ProcessExplorer.html"><img border="0" src="http://blogmarks.net/screenshots/2006/09/16/e4b493127f722ca8ad7492c96d79b6c8.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.sysinternals.com/Utilities/ProcessExplorer.html">Process Explorer</a></h4>
 
by <a href="http://blogmarks.net/user/Riduidel">Riduidel</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/251455">9 other(s)</a> 
<p class="description">Ever wondered which program has a particular file or directory open? Now you can find out. Process Explorer shows you information about which handles and DLLs processes have opened or loaded.

The Process Explorer display consists of two sub-windows. The top window always shows a list of the currently active processes, including the names of their owning accounts, whereas the information displayed in the bottom window depends on the mode that Process Explorer is in: if it is in handle mode you’ll see the handles that the process selected in the top window has opened; if Process Explorer is in DLL mode you’ll see the DLLs and memory-mapped files that the process has loaded. Process Explorer also has a powerful search capability that will quickly show you which processes have particular handles opened or DLLs loaded.

The unique capabilities of Process Explorer make it useful for tracking down DLL-version problems or handle leaks, and provide insight into the way Windows and applications work.

Process Explorer works on Windows 9x/Me, Windows NT 4.0, Windows 2000, Windows XP, Server 2003, and 64-bit versions of Windows for x64 processors, and Windows Vista.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/freeware">freeware</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/software">software</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/windows">windows</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/process">process</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/system">system</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=171641">Copy</a> | 
<a href="http://blogmarks.net/link/251455">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/multilinko/mark/135901">
<title>Sympatico / MSN Technology : Digital Living : Articles : HP Power saving tips</title>
<link>http://technology.sympatico.msn.ca/DigitalLiving/Articles/HP_Power_saving_tips.htm</link>
<description>The biggest standby loss of energy, sometimes referred to as &quot;leaking electricity,&quot; occurs in modern consumer electronics.

Even when your television is turned off, it's really in standby mode so that it can respond to your remote control. Along with TVs, VCRs, cable boxes, and satellite dishes account for the largest share of a home's leaking electricity, roughly 35 percent. Audio equipment makes up another 25 percent of standby losses; a small compact audio unit can draw 9 watts while it's ostensibly turned off. Communications equipment such as answering machines, cordless phones, and fax machines are responsible for an additional 10 percent of home electricity losses.

Today's estimates say that the average household constantly leaks about 50 watts of electricity. Right now, the only way to prevent some appliances from leaking electricity is to unplug them when they might not be in use for a long period of time.

Watts wrong
According to the EPA, lighting accounts for approximately 24 percent of total end-use consumption of electricity in commercial offices, the largest piece of the energy consumption pie. Making sure to turn off lights when you have left the room is the easiest thing you can do to reduce your energy costs. The problem isn't so much the amount of time they are left on but the inefficiency of incandescent light bulbs.</description>
<dc:date>2005-08-16T11:06:24Z</dc:date>
<dc:author>multilinko</dc:author>
<dc:subject>audio, light, digital, energy</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://technology.sympatico.msn.ca/DigitalLiving/Articles/HP_Power_saving_tips.htm"><img border="0" src="http://www.blogmarks.net/screenshots/2005/08/16/30a91b3e55e4823f4f702a6f27fa7a3d.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://technology.sympatico.msn.ca/DigitalLiving/Articles/HP_Power_saving_tips.htm">Sympatico / MSN Technology : Digital Living : Articles : HP Power saving tips</a></h4>
 
by <a href="http://blogmarks.net/user/multilinko">multilinko</a> 
<p class="description">The biggest standby loss of energy, sometimes referred to as "leaking electricity," occurs in modern consumer electronics.

Even when your television is turned off, it's really in standby mode so that it can respond to your remote control. Along with TVs, VCRs, cable boxes, and satellite dishes account for the largest share of a home's leaking electricity, roughly 35 percent. Audio equipment makes up another 25 percent of standby losses; a small compact audio unit can draw 9 watts while it's ostensibly turned off. Communications equipment such as answering machines, cordless phones, and fax machines are responsible for an additional 10 percent of home electricity losses.

Today's estimates say that the average household constantly leaks about 50 watts of electricity. Right now, the only way to prevent some appliances from leaking electricity is to unplug them when they might not be in use for a long period of time.

Watts wrong
According to the EPA, lighting accounts for approximately 24 percent of total end-use consumption of electricity in commercial offices, the largest piece of the energy consumption pie. Making sure to turn off lights when you have left the room is the easiest thing you can do to reduce your energy costs. The problem isn't so much the amount of time they are left on but the inefficiency of incandescent light bulbs.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/audio">audio</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/light">light</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/digital">digital</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/energy">energy</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=135901">Copy</a> | 
<a href="http://blogmarks.net/link/197714">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>