What Every Programmer Should Know About Memory Ulrich Drepper Red Hat, Inc. drepper@redhat.com November 21, 2007 Abstract As CPU cores become both faster and more numerous, the limiting factor for most programs is now, and will be for some time, memory access. Hardware designers have come up with ever more sophisticated memory handling and acceleration techniques–such as CPU caches–but these canno
I recently landed a new version of DMD on mozilla-central. DMD is a tool helps us understand and thus reduce Firefox’s memory consumption. But in order to understand DMD, you first have to understand about:memory. about:memory The MemShrink project started about 18 months ago, and it has been very successful in reducing Firefox’s memory consumption. about:memory is MemShrink’s not-so-secret wea
Tracking Down Memory Leaks in Node.js – A Node.JS Holiday Season This post is the first in the A Node.JS Holiday Season series from the Identity team at Mozilla, who last month delivered the first beta release of Persona. To make Persona, we built a collection tools addressing areas ranging from debugging, to localization, to dependency management, and more. This series of posts will share our lea
Categories Chrome (1) compassion (1) cooking (1) esp (2) newsletter (8) outparams (2) Project Management (3) spidermonkey (3) SquirrelFish (1) Thoughts (3) treehydra (3) Uncategorized (44) TraceMonkey (2) Archive July 2012 (1) May 2012 (2) April 2012 (2) March 2012 (1) February 2012 (1) January 2012 (1) December 2011 (2) November 2011 (4) August 2011 (2) July 2011 (1) June 2011 (2) Ma
TL;DR: Cross-browser comparisons of memory consumption should be avoided. If you want to evaluate how efficiently browsers use memory, you should do cross-browser comparisons of performance across several machines featuring a range of memory configurations. Cross-browser Memory Comparisons are Bad Various tech sites periodically compare the performance of browsers. These often involve some cross
$200K 1 10th birthday 4 abusive ads 1 abusive notifications 2 accessibility 3 ad blockers 1 ad blocking 2 advanced capabilities 1 android 2 anti abuse 1 anti-deception 1 background periodic sync 1 badging 1 benchmarks 1 beta 83 better ads standards 1 billing 1 birthday 4 blink 2 browser 2 browser interoperability 1 bundles 1 capabilities 6 capable web 1 cds 1 cds18 2 cds2018 1 chrome 35 chrome 81
This page explains coding patterns that cause extension to cause memory leaks. Causes of zombie compartments Zombie compartments are a particular kind of memory leak. All zombie compartments in extensions are caused by a failure to release resources appropriately in certain circumstances, such as when a window is closed, a page unloads, or an extension is disabled or removed. While bug 695480 sho
Today I want to announce a new extension for Firefox. It’s been developed by the Mozilla QA Automation Services team, which exists to support the Mozilla QA community by developing tools and frameworks for ease of testing. And this time, in case of the extension, we even target (web) developers, and our huge Firefox user base. So what is it about? Mid of December 2011 bug 711900 has been filed. It
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く