On Tue, May 16, 2017 at 01:33:13AM -0500, Tom Ritter wrote:
> My interest in jemalloc3/4 has always been with taking advantage of
> it's partitioning capabilities to segment things like javascript
> arrays for increased security against heap grooming and UAF
> exploitation.
>
> Is there a path for
My interest in jemalloc3/4 has always been with taking advantage of
it's partitioning capabilities to segment things like javascript
arrays for increased security against heap grooming and UAF
exploitation.
Is there a path forward with this in mozjemalloc? Plans, or would-take
changes, or just tho
According to Alexa top 100 Taiwan sites and quick spot checks, I can only
see the following two sites encoded in Big5:
http://www.ruten.com.tw/
https://www.momoshop.com.tw/
Both are shopping sites (eBay-like and Amazon-like) so you get the idea how
forms are used there.
Mike reminded me to check
Having been involved with jemalloc 3/4/5 work as well, I agree with Mike's
conclusions.
-e
On Mon, May 15, 2017 at 6:19 PM, Nicholas Nethercote wrote:
> Just to add some context: glandium is deeply familiar with jemalloc4's
> internals, having submitted numerous patches and fixes to it. And he
Just to add some context: glandium is deeply familiar with jemalloc4's
internals, having submitted numerous patches and fixes to it. And he has
spent *significant* time and effort on multiple occasions, on multiple
versions of jemalloc4, trying to avoid the performance regressions, without
success.
I thought there was a bug on file, but maybe not. I've long thought the
following changes should be made:
* `mach mercurial-setup` should be rolled into `mach bootstrap`
* `mach doctor` should be rolled into `mach bootstrap`
* `mach bootstrap` should remember answers from last time and not prompt
Hi,
We've tried to get off mozjemalloc for, apparently, close to 5 years
(date of the filing of bug 762449). We've had memory usage regressions
(like bug 1219914), and we've had perf regressions as per talos numbers
(things like bug 1138999), and those have never gone away (with
variations with ea
The stand-alone bootstrap.py script actually has a --no-interactive
option (which answers 'yes' to everything) but the mach wrapper
doesn't support this.
`mach mercurial-setup` takes an --update-only option. Maybe we
implementing something like that for `mach boostrap` would help. Or
calling it so
Actually, I think my real question is "What is the intended way for
developers to keep their development environment up-to-date?" I don't think
that way should require a developer to answer questions, because the
answers presumably haven't changed since the last time they answered them.
If the inte
I think this deserves a round of applause. Its a large undertaking with
measurable perf wins in areas with strong SEP(1) fields
1. https://en.wikipedia.org/wiki/Somebody_else%27s_problem
/Sam
On Wed, May 10, 2017 at 7:09 PM, Florian Quèze wrote:
> On Mon, Mar 27, 2017 at 9:42 PM, Dave Townse
On 5/12/17 6:16 PM, Gregory Szorc wrote:
Isn't that something that mach bootstrap should be doing?
Yes. A patch is in Ryan's review queue to do this.
Said patch is now merged to mozilla-central! :-)
-Ryan
___
dev-platform mailing list
dev-platfor
On 12/05/17 08:46, Anne van Kesteren wrote:
> For about five years I've been trying to figure out the IDNA algorithm
> that a) browsers follow and b) browsers want to follow, but I've not
> had much luck thus far getting folks to reply. E.g.,
> https://lists.w3.org/Archives/Public/www-archive/2017F
There's an old bug about this
https://bugzilla.mozilla.org/show_bug.cgi?id=469421 but no ETA (I also
suspect a Library redesign may happen after Photon)
On Sun, May 14, 2017 at 10:34 AM, wrote:
> Hi,
>
> When searching for a bookmark we don't have any information about the
> folder.
> It could b
On Fri, May 12, 2017 at 4:28 AM, Kan-Ru Chen wrote:
> On Thu, May 11, 2017, at 01:43 PM, Henri Sivonen wrote:
>> In Firefox 43, I rewrote our Big5 support and, among other things, I
>> optimized the *encoder* for footprint rather than speed on the theory
>> that users won't notice anyway since the
Hi everyone,
Here's the list of new issues found and filed by the Desktop Release QA
Team last week, May 8 - May 12 (week 19).
Additional details on the team's priorities last week as well as the
plans for the current week are available at:
https://public.etherpad-mozilla.org/p/DesktopManual
15 matches
Mail list logo
