Hello, just to be sure that this problem do not get lost and because the thread is closed because it was in the 5.6 beta section:
From :PieterAlbers
Answer from LeonhardP :
It has been reported a month ago and it’s still not fixed.
Everything seem to be fine with the webassembly exepting this problem. My game run fine but crash because of this problem.
Thank you.
Yes,its been almost 1.5 months and we cannot test webassembly on our games yet, even Browsers also launched webassembly more than 1 month ago.
Can you tell us if you are working on this issue or not?
It has been submitted a month ago, and it’s still not fixed.
Thank you.
Yes, we are.
@roka - Thanks for not forgetting this!
Your welcome, i just want to be able to use my unity version as it should be.
It’s crazy to see a bug reported a month ago during the beta not fixed yet …
Do we happen to know if this will be part of a patch release? (fingers crossed)
From schubkraft :
Funny no? ^^
Yeah… hilarious 
would be ‘nice’ indeed if these fixes would be included in a 5.6 patch or release
Yep
Was hoping this would be fixed in 2017.1.b6 but no dice. Can anyone provide an estimate on which beta release will contain this fix?
This is preventing us from moving forward in WebAssembly and we have specifically upgraded (see: purchased) to a 2017 subscription on the assumption that this will be addressed soon.
Thanks.
I don’t see how a 2017 subscription changes anything. You still get the exact same version of Unity everyone else does. Licenses and extra services change, not the engine.
Also the developer has clearly stated it it’s being worked on. Times cannot be given because it’s not up to the developer when it lands.
Fixes have to go through a peer review process and may interfere with other fixes. Just be patient.
With all due respect, when Unity heavily touts exciting features in their PR and GDC presentations (such as WebGL support in 5.x and WebAssembly in 5.6) and then users discover fatal errors right off the bat that then require updates to new versions of Unity, it becomes very frustrating. WebAssembly is “experimental” in 5.6 so YES an upgrade to 2017 is required if we want full WebAssembly support (eventually).
I understand that it’s a business and there are thousands of factors that influence release schedules, many of which are out of the control of Unity dev (i.e, browser vendors), so I can accept the upgrade requirement. But I don’t think its too much to ask for a possible timeline when the developer response on this specific issue is:
All the support I’ve received from developers on this forum has been cordial, helpful and responsive thus far, even when they need to be vague. “Just be patient” helps noone.
The issue has been fixed but, as @hippocoder said, all changes need to go through a review process which is happening right now. So far everything is looking good for the fix to land to 5.6 and 2017.1 by the end of the month or in early June.
Awesome! I totally understand the review process and my apologies if I was sounding pushy. Just curious.
Thanks, Marco.
@sirrus One more comment: we just found a new bug in 2017.1b2 that looks really similar: Unity Issue Tracker - [WebAssembly] Integer overflow on DirectorFrameTime::CalculateDSPDeltaTime
which we are still investigating. So, for the time being I recommend that you stick with 5.6
OK, thanks for the heads up.
Hopefully, it gets released this week, “Early June” as Marco mentioned 
https://issuetracker.unity3d.com/issues/wasm-runtime-error-integer-overflow-slash-unrepresentable is scheduled for 5.6.1p3 (along with other bug fixes)
https://issuetracker.unity3d.com/is…ow-on-directorframetime-calculatedspdeltatime is being fixed now.