integer overflow/integer

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.

 

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

 

Awesome! I totally understand the review process and my apologies if I was sounding pushy. Just curious.

Thanks, Marco.

 

OK, thanks for the heads up.

 

Hopefully, it gets released this week, "Early June" as Marco mentioned

 

Thanks for your response.

 

okay

 

Looks like this bug got fixed in latest beta version https://unity3d.com/unity/beta?_ga=2.227942622.298475358.1497148684-451998078.1496148513
Havn't tried it yet though,gonna try today.

 

Damn, loading assetbundles in b9 is always giving error, even in editor and webgl(offcourse i recompiled bundles with this new unity version)

 

https://pastebin.com/T6byvngg

@Marco-Trivellato So i went deeply and found the issue which is listed in pastebin link as comments, Thats really weird in Unity 5.6b9, Editor and compiled version.​

 

For my part, it happen when i instanciate a prefab (an explosion) with an audio source with "Play on awake" checked

 

We are yet getting integer overflow bug in b9 during the scene change, mostly when the loaded scene is big enough(can say when memory jump occurs in game) or when instantiating a lot of players one after another on joining rooms,for instance in multiplayer games( offcourse asm.js works fine), now i started giving up on webassembly and webgl

 

@Marco-Trivellato Here is the stacktrace :
exception thrown: RuntimeError: integer result unrepresentable,RuntimeError: integer result unrepresentable
at __ZN17DirectorFrameTime21CalculateDSPDeltaTimeEv (<WASM>[5729]+677)
at __ZN15DirectorManager12OnSampleTimeEv (<WASM>[5727]+143)
at __ZZN15DirectorManager15InitializeClassEvEN40EarlyUpdateDirectorSampleTimeRegistrator7ForwardEv (<WASM>[5703]+26)
at __Z10PlayerLoopv (<WASM>[6083]+920)
at __ZL8MainLoopv (<WASM>[6070]+248)
at dynCall_v (<WASM>[64745]+11)
at Object.UnityLoader.797615e9914df39e318dca8456244e4e.Module.dynCall_v (blob:http://storage-direct.id.net/55144286-9208-4fe7-9ded-cd4182d83608:20924:86)
at browserIterationFunc (blob:http://storage-direct.id.net/55144286-9208-4fe7-9ded-cd4182d83608:2707:30)
at Object.runIter (blob:http://storage-direct.id.net/55144286-9208-4fe7-9ded-cd4182d83608:2824:13)
at Browser_mainLoop_runner (blob:http://storage-direct.id.net/55144286-9208-4fe7-9ded-cd4182d83608:2762:26)

Can you spot the problem ? looks similar to:

1. https://issuetracker.unity3d.com/is...00.1882648136.1497359872-929948973.1497359872

2. https://issuetracker.unity3d.com/is...00.1882648136.1497359872-929948973.1497359872

When can we expect to get it fixed i guess this is the last Big Stone on the way. if it can be fixed in one of the next beta's or patches,that will be really awesome

 

Thank you ! Appreciated

 

1. https://issuetracker.unity3d.com/is...00.1882648136.1497359872-929948973.1497359872
2. https://issuetracker.unity3d.com/is...00.1882648136.1497359872-929948973.1497359872

Issue 1: It says its fixed in Unity 2017.1, why cant it be included in next beta release of Unity 2017.1 i.e Unity 2017.1b10.
Issue 2: Not yet fixed in 5.6.1p4.

Can both(or atleast Issue 1) be fixed in next beta release of Unity 2017.1(b10), so atleast we can start benchmarking webassembly sooner.

Also beta version Unity 2017.1b10 wasnt released this weekend(i expected 'Issue1' to be fixed in beta 10), thinking if it was on weekly release scenario yep. @Marco-Trivellato

 

So b10 was released yesterday and it didnt had back-ported fix of Issue #1(read release notes only and it didnt had that bug tracking number, or bug is fixed but not listed in Release notes?), so all eyes on b11 next week

 

Any ETA on Unity 2017.1 b11 approximation release date?

 

So Unity 2017.1f1 has that Issue#1 resolved, Thanks Marco! , though i have been using Unity 5.x license, i hope Issue #1 listed above, isn't present in Unity 5.6.2 (https://unity3d.com/unity/whats-new/unity-5.6.2) , will post here if it does exist.

 

@Marco-Trivellato

Unity 2017.1.f1 works fine, without any issues.

Unity 5.6.2 gives error:
UnityLoader.js:1 exception thrown: RuntimeError: memory access out of bounds,RuntimeError: memory access out of bounds at <WASM UNNAMED> (<WASM>[12525]+134) at <WASM UNNAMED> (<WASM>[12524]+15) at <WASM UNNAMED> (<WASM>[13195]+77) at <WASM UNNAMED> (<WASM>[55915]+52) at <WASM UNNAMED> (<WASM>[38009]+246) at <WASM UNNAMED> (<WASM>[38008]+258) at <WASM UNNAMED> (<WASM>[33398]+1747) at <WASM UNNAMED> (<WASM>[26679]+258) at <WASM UNNAMED> (<WASM>[26973]+109) at <WASM UNNAMED> (<WASM>[41079]+22) at <WASM UNNAMED> (<WASM>[61885]+19)

This happens when scene bundle gets loaded.
Unit Editor gets crashed as well, and we have to reopen unity.

 

Unrelated to this thread, Unity UI isnt visible in webassembly and webgl when compiled from Unity 2017.2.0b3, though works fine in Unity2017.1.0f3.

Not related to this thread, but worth mentioning, not have enough time to create a thread for now.

 

For some other project, Getting this error in webassembly, though asm.js works fine.
Version: Unity5.6.2 & Unity2017.1.0f3.

exception thrown: RuntimeError: integer overflow,__ZN4FMOD7Channel12setFrequencyEf@blob:null/709b5e21-0d78-8b4d-b0ce-3c79de0f616d:1443278:1

__ZN20SoundChannelInstance11UpdatePitchEv@blob:null/709b5e21-0d78-8b4d-b0ce-3c79de0f616d:1442308:1

__ZN20SoundChannelInstance14SetFMODChannelEPN4FMOD7ChannelE@blob:null/709b5e21-0d78-8b4d-b0ce-3c79de0f616d:1438537:1

__ZN12SoundManager6UpdateEv@blob:null/709b5e21-0d78-8b4d-b0ce-3c79de0f616d:1436353:1

__ZN11AudioModule6UpdateEv@blob:null/709b5e21-0d78-8b4d-b0ce-3c79de0f616d:1571144:1

__ZZL31InitializeAudioManagerCallbacksvEN36PostLateUpdateUpdateAudioRegistrator7ForwardEv@blob:null/709b5e21-0d78-8b4d-b0ce-3c79de0f616d:1570973:1

__Z10PlayerLoopv@blob:null/709b5e21-0d78-8b4d-b0ce-3c79de0f616d:2126830:1

__ZL8MainLoopv@blob:null/709b5e21-0d78-8b4d-b0ce-3c79de0f616d:2118609:1

dynCall_v@blob:null/709b5e21-0d78-8b4d-b0ce-3c79de0f616d:16464825:1

UnityLoader.e0906dda2ec51efd78a5269d0fad9255/Module.dynCall_v@blob:null/709b5e21-0d78-8b4d-b0ce-3c79de0f616d:19770:59

browserIterationFunc@blob:null/709b5e21-0d78-8b4d-b0ce-3c79de0f616d:2707:11

runIter@blob:null/709b5e21-0d78-8b4d-b0ce-3c79de0f616d:2824:13

Browser_mainLoop_runner@blob:null/709b5e21-0d78-8b4d-b0ce-3c79de0f616d:2762:9

 

Yes, its reproducable with this patch as well.

 

@Marco-Trivellato I havnt done any bug reports in the past, but i uploaded a wasm_pitch_bug.unitypackage to this post(used Unity2017.1.0p5 for this package), which you can compile with wasm and try in browsers.

Wasm gives an error(stack trace listed in above messages) while asm works fine as expected.

Compiled builds:
WASM: https://www.dropbox.com/s/z72zunn9n64d3ac/wasm_pitch_compiled.zip?dl=0
WASM development: https://www.dropbox.com/s/d9sygzb8xzr2evw/wasm_pitch_compiled_development.zip?dl=0
ASM: https://www.dropbox.com/s/fd8tkibxlgis7ty/asm_pitch_compiled.zip?dl=0