I had a dozen devs in my team all hit the reload button for ten times, now. For those who were still on on 51 the error came almost immediately, but just for the first time they loaded the page. For those who then upgraded the error did not reappear, *except for one guy* with this browser: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.82 Safari/537.36
So, yes the bug still occurs with Chrome 52, although interestingly we only get to see the "second" exception now, but not the stackoverflow anymore - and it became even more difficult to reproduce :-( I'll continue to investigate this. 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.
