Thank you so much for always tracking this, indeed I get no feedback from chrome team yet.
No, I have't find out the exact position of bug-causing code, but I tested this page also on the safari, and it also works well, so very likely to be a "64 bits of chrome only" bug. I will learn how to debug the codes and locate the possible location. p.s. the emscripten is really awesome~ Thanks, Eden On Friday, November 6, 2015 at 6:48:09 AM UTC+8, Alon Zakai wrote: > > I also see an error in chrome (all I have is 64-bit). > > But I would recommend reducing this to as small a testcase before filing > it, as otherwise it is not likely to get much attention from the chrome > devs, in my experience. Have you found where in libtheora the problem > happens? > > On Thu, Nov 5, 2015 at 3:03 AM, Eden Zhao <[email protected] > <javascript:>> wrote: > >> one can using the attached page to reproduce this bug by: >> 1) open the html page >> 2) open console >> 3) click on the start test button >> >> expect result: >> see all test passed(true for 32bits of chrome and firefox) >> >> actual result:(on 64bits of chrome) >> see some of the case failed, and the output might be different for each >> execution, and change JS codes outside the lib will cause the lib output >> change too, so might have some memory disorder. >> >> Best Regards, >> Eden >> > > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" 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.
