thanks - I'll consider this. Indeed when I copied my Chrome version number I immediately got a Chrome update (since when doesn't Chrome auto-update anymore immediately - the last few times I always had to first check the about dialog before it updated) I haven't been able to repro the bug with my test-case anymore. I was expecting it to fail because 10 days ago a customer who found the issue reported that it also happens with his then-current Canary version. That's why I thought it probably wouldn't be fixed with 52, but so far it indeed is looking good. I'll keep on testing. Do you have a specific bug-fix or changeset in mind that could affect my issue?
Am Freitag, 22. Juli 2016 13:21:29 UTC+2 schrieb Jakob Kummerow: > > On Fri, Jul 22, 2016 at 12:00 PM, <[email protected] <javascript:>> > wrote: > >> I cannot just upload my larger test-case publicly because it contains >> code parts that I cannot easily publish due to licensing restrictions. Is >> there a way I can non-publicly share that code with the V8 team? >> > > Put it up behind some kind of login and send us the credentials for a test > account? Or send the code in off-list email if you prefer. > > Also, does the bug still occur with Chrome 52? > > -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
