Despite making some serious headway on the Dojo memory leak issues, my head is entirely enshrouded in a sleep-deprived fog. Really need to do something about it.
-
What’s All This Then?
I'm Alex Russell, a web developer working on Chrome, Blink, and the Web Platform at Google. I'm guilty of many JavaScript transgressions.
I help lead the team building a new application model for the web, and serve on ECMA TC39 (the standards body for JavaScript). I'm an elected member of the W3C Technical Architecture Group and am Tech Lead for Standards inside the Chrome team. I design and advocate for extensible, layered, data-driven evolution of the web platform.
My professional aim is to make the web a better platform and to the extent that I can keep politics and economics from creeping in, that's what this blog is about.
Other facets available upon HTTP request: twitter, facebook, flickr, linkedin, lanyrd, and quora. Expect less self-restraint there.
I'm proud husband to Frances Berriman. We live and work in San Francsico.
-
Recent Comments
- Peter Rushforth on Effective Standards Work, Part 2: Threading the Needle
- alex on Can You Afford It?: Real-world Web Performance Budgets
- Riya Sharma on Can You Afford It?: Real-world Web Performance Budgets
- Jonathan Danylko on Can You Afford It?: Real-world Web Performance Budgets
- Shane Labs on Can You Afford It?: Real-world Web Performance Budgets
- John on Can You Afford It?: Real-world Web Performance Budgets
- Naura on Can You Afford It?: Real-world Web Performance Budgets
- Tarun Elankath on Can You Afford It?: Real-world Web Performance Budgets
- alex on Can You Afford It?: Real-world Web Performance Budgets
- Tyler Reitz on Can You Afford It?: Real-world Web Performance Budgets
3 Comments
You could start by adding optional path support to loadModule! ;)
Did you try Joel Webber’s Drip? I managed to find one memory leak in Bindows using it so it already paid for its price ;-)
I’ve tried Drip, but it seems to “lie” about Dojo. Doing things that actually reduce leakage show up in the memory footprint listing, but nodes that don’t leak still show up in the “leaked” list.
On the upside, I got 13 hours of sleep last night, so I’m at least 1 for 2. = )