Re: Memory management in features implemented in JS

2014-03-24 Thread Steve Fink
On 03/19/2014 04:39 PM, Kyle Huey wrote: Followup to dev-platform please. We are discovering a lot of leaks in JS implemented DOM objects. The general pattern seems to be that we have a DOM object that also needs to listen to events from the message manager or notifications from the

Re: Memory management in features implemented in JS

2014-03-24 Thread Jim Blandy
On 03/23/2014 12:17 AM, Boris Zbarsky wrote: Say we have this: observerService.addSettingObserver(data-changed, obj, cache, null) and someone sets a data-changed notification. If I understand your proposal correctly, that will do some equivalent of obj.cache = null, assuming obj is still

Re: Memory management in features implemented in JS

2014-03-24 Thread Jim Blandy
On 03/23/2014 10:56 PM, Steve Fink wrote: Anyway, with your specific example, it seems to me that the problem is that you're losing information. The popups need the main window to communicate with each other, and the main window needs all of its stuff to work while it's open. The solution, then,

Re: Memory management in features implemented in JS

2014-03-24 Thread Jason Orendorff
On 3/24/14, 2:42 AM, K. Gadd wrote: It is, however, my understanding that cycle collections in SpiderMonkey are separate from non-cycle-collections and occur less often; is that still true? There are two collectors. The JS engine's garbage collector runs more frequently. It collects cycles

Re: Memory management in features implemented in JS

2014-03-24 Thread Jim Blandy
On 03/24/2014 12:55 AM, Jason Orendorff wrote: and blow that whole window out the air lock. Actually, we nuke it from orbit. It's the only way to be sure. ___ dev-platform mailing list dev-platform@lists.mozilla.org

Re: Memory management in features implemented in JS

2014-03-24 Thread Karl Tomlinson
Jason Orendorff writes: On 3/24/14, 2:42 AM, K. Gadd wrote: There are two collectors. The JS engine's garbage collector runs more frequently. The XPCOM cycle collector runs less often. That may be true in some scenarios, but I sometimes observe the cycle collector running more frequently

Re: Proposed W3C Charter: Timed Text Working Group (WebVTT and TTML)

2014-03-24 Thread Robin Berjon
On 22/03/2014 07:30 , L. David Baron wrote: I'm inclined to think that it's not worth putting up a massive fight over the group's organization here, which I think is what it would take to change this plan. I think I'd rather focus the bandwidth of our communication with W3C management on other

Rendering meeting, Monday (today) 5:30pm PDT (the later time)

2014-03-24 Thread Milan Sreckovic
The Rendering meeting is about all things Gfx, Image, Layout, and Media. It takes place every second Monday, alternating between 2:30pm PDT and 5:30pm PDT. The next meeting will take place today, Monday, March 24 at 5:30 PM US/Pacific Please add to the agenda:

Having more control over when an IPDL message is compressed

2014-03-24 Thread Botond Ballo
Hello dev-platform, I recently fixed an APZ bug [1] that was caused by an IPDL message, PBrowser::UpdateFrame, being compressed when it shouldn't have been. I think the compression was correct back when we didn't have subframe scrolling, and so all messages pertained to the same frame, in which

Intent to ship: Path2D + addition canvas APIs

2014-03-24 Thread Rik Cabanier
Path2D is a new object in the global namespace. Its main use case is to cache path segments. For instance, shumway could use it to cache the flash edgelists which should increase its drawing performance. Eventually it will act as a bridge between SVG and Canvas but for now its use is limited to