Re: Effects of JSM Compartments on Performance and Development Practices

2013-01-20 Thread David Rajchenbach-Teller
I have some shared concerns, given that I am one of the persons involved in the ongoing heavy refactoring on Session Restore, which for some users needs to deal with 50Mb+ strings sent across JSMs. At the moment, my main worry is not memory usage (yet) but string copying. Cheers, David signat

Re: The state of the Aurora branch

2013-01-20 Thread Ehsan Akhgari
On 2013-01-20 9:40 PM, Nicholas Nethercote wrote: Of the three options I present, the one that I think has the strongest support and least opposition among the developers investigating the problems is option 2: # (2) Disable the testpilot extension on aurora using the patch in # comment 48

Re: The state of the Aurora branch

2013-01-20 Thread Nicholas Nethercote
>> Of the three options I present, the one that I think has the >> strongest support and least opposition among the developers >> investigating the problems is option 2: >> >> # (2) Disable the testpilot extension on aurora using the patch in >> # comment 48, and reopen mozilla-aurora. comment

Re: The state of the Aurora branch

2013-01-20 Thread Justin Wood (Callek)
Ed Morley wrote: > On 19 January 2013 15:01:09, Ehsan Akhgari wrote: >> dbaron posted a summary of our options on release-drivers > > Please can that be posted somewhere public for those of us not on > release-drivers? Not seeing anything that need be kept private, I'll forward a post or two her

Re: Effects of JSM Compartments on Performance and Development Practices

2013-01-20 Thread Joshua Cranmer
On 1/20/2013 1:37 PM, Gregory Szorc wrote: I'm writing to the Platform list as a developer that maintains a significant amount of JavaScript for Firefox. Much of the JavaScript I maintain is for large backend features, such as Sync and Firefox Health Report. These features are thousands of line

Re: Effects of JSM Compartments on Performance and Development Practices

2013-01-20 Thread Justin Lebar
We've had bug 764220 open on the CPG memory regression for six months now. Although it's a MemShrink:P1, it hasn't gotten the attention it deserves. FWIW, I think part of this stems from the fact that the MemShrink team is often ineffective at getting others to fix bugs that we think are a priori

Effects of JSM Compartments on Performance and Development Practices

2013-01-20 Thread Gregory Szorc
I'm writing to the Platform list as a developer that maintains a significant amount of JavaScript for Firefox. Much of the JavaScript I maintain is for large backend features, such as Sync and Firefox Health Report. These features are thousands of lines of code (mostly JavaScript) and interact