Harmony helpwanted: Proxy, Map discrepancy between V8 and SpiderMonkey

Alex Vincent ajvincent at gmail.com
Wed Mar 21 13:00:31 PDT 2012


I reduced the testcase quite severely.  It's a combination between Proxy
and WeakMap.  I store the proxy as a key for the WeakMap, and then expect
to get back that proxy through Object.getPrototypeOf.

On Tue, Mar 20, 2012 at 7:29 AM, Andreas Rossberg <rossberg at google.com>wrote:

> On 20 March 2012 08:18, Alex Vincent <ajvincent at gmail.com> wrote:
>> Hi, everyone.  I've been tinkering around with Harmony's Proxy and
>> WeakMap implementations, and I've run into a problem.  A Jasmine test which
>> works fine in Mozilla Firefox Aurora builds throws an exception in Google
>> Chrome Dev builds, with the experimental JavaScript features enabled.
>> I really need some help in identifying whether the bug is in Aurora,
>> Chrome, or in my own code.  I wrote all of the JavaScript code in the
>> project, and to my knowledge none of it is browser- or engine-specific; it
>> should all conform to Harmony and ECMAScript standards unless I have a bug
>> in my code.
> Proxies are rather new, so it might very well be a bug in V8. There might
> also be minor implementation differences between the two systems, since the
> proxy spec wasn't entirely complete yet and has changed in some details,
> even before the advent of direct proxies.
> I would need a small enough test case to verify that. Is there a chance
> that you can narrow down the exact point where the behaviours of Firefox
> and Chrome start to differ unexpectedly? For example, with some printf
> debugging?
> /Andreas

"The first step in confirming there is a bug in someone else's work is
confirming there are no bugs in your own."
-- Alexander J. Vincent, June 30, 2001
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20120321/6c35f979/attachment.html>

More information about the es-discuss mailing list