On Mon, Feb 10, 2014 at 8:24 AM, Kannan Vijayan <[email protected]> wrote: > > The collision rate control is the bad behaviour I'm referring to. If a > webapp is written so as to allow a user to generate atoms (not too hard > since they get created in a bunch of places, esp. property-access related > operations), the user can take advantage of it to pollute the atoms table > with arbitrarily many entries that are trivially constructed to have the > same hash code.
Well, yes. It's a potential performance fault, albeit a rather obscure one. I've used N=1000 in my patch, so the source code would have to contain *many* literal strings or identifiers of length greater than 1000 whose first 1000 chars are all the same in order to adversely affect the collision rate. More generally, "make it impossible to write code that performs badly" isn't a worthy or feasible goal, IMO. Nick _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
