Thanks! I'll cc some people.

On Fri, Apr 19, 2019 at 11:05 AM Floh <[email protected]> wrote:

> Ok, here's the link to the Chromium issue:
> https://bugs.chromium.org/p/chromium/issues/detail?id=954542
>
> On Friday, 19 April 2019 01:08:45 UTC+2, Alon Zakai wrote:
>>
>> This could be a Chrome regression. Rick, which OS are you on? (other
>> issue was Windows-only I believe)
>>
>> Floh, I think you said on Twitter you'd file a Chromium issue - is there
>> a link to that?
>>
>> On Thu, Apr 18, 2019 at 2:58 PM Rick Battagline <[email protected]>
>> wrote:
>>
>>> Is this a problem with a more recent version of emscripten?  I have some
>>> code that is compiling and running fine for me, but I just tried to help my
>>> brother install emscripten and the same code is resulting in "Oh Snap"
>>> errors on Chrome (not on Firefox).
>>>
>>> what is up with that btw?  Those "Oh Snap" messages are totally useless.
>>>
>>> Thanks
>>>
>>>
>>> On Tuesday, April 16, 2019 at 2:57:42 AM UTC-6, Floh wrote:
>>>>
>>>> I stumbled over an "interesting" problem yesterday when doing some
>>>> fixes for the Dear ImGui emscripten sample code:
>>>>
>>>> https://github.com/ocornut/imgui/tree/master/examples/example_emscripten
>>>>
>>>> On Chrome 73 and Canary 75, Windows only (tested on Win7 and Win10),
>>>> the sample immediately Aw Snaps when compiled
>>>> with -O2 and -O3, but works alright when compiled with -Os or -O1.
>>>> Firefox works, Chrome on Mac and Linux works too.
>>>>
>>>> Here are the various links:
>>>>
>>>> -Os (works):
>>>> http://floooh.github.io/oryol-sticky-tests/emsc-imgui-test/example_emscripten.html
>>>>
>>>> -O1 (works):
>>>> http://floooh.github.io/oryol-sticky-tests/emsc-imgui-test/example_emscripten_o1.html
>>>>
>>>> -O2 (Aw Snap):
>>>> http://floooh.github.io/oryol-sticky-tests/emsc-imgui-test/example_emscripten_o2.html
>>>>
>>>> -O3 (Aw Snap):
>>>> http://floooh.github.io/oryol-sticky-tests/emsc-imgui-test/example_emscripten_o2.html
>>>>
>>>> Compiled with emscripten 1.38.30
>>>>
>>>> I'm currently suspecting that the problem is somehow caused by SDL2,
>>>> because that's the difference to my own ImGui samples which work fine
>>>> (however I'm usually compiling my own stuff with the emscripten incoming
>>>> version, but I definitely would have noticed the problem earlier, when
>>>> 1.38.30 was still in incoming).
>>>>
>>>> I haven't written any Chrome bugreports yet (let me know if I should).
>>>>
>>>> -Floh.
>>>>
>>> --
>>> 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.
>>>
>> --
> 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.
>

-- 
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.

Reply via email to