Search Issue Tracker
Not Reproducible
Votes
1
Found in
5.0.1f1
Issue ID
690090
Regression
No
The file 'MemoryStream' is corrupted! Remove it and launch unity again! [Position out of bounds
This issue has no description.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Character spacing value is not applied when using a specific font asset
- [Android][IL2CPP] Player crashes on __memcpy_aarch64_simd+276 when invoking native code via a plugin on some ARM64 Android devices
- [Android]Resources fail to load when the AAB build contains a large Addressables Bundle
- Unity is loading internal version of SharpZipLib instead of local version
- The Context Menu items are ordered incorrectly
mosnang
Jan 28, 2016 18:39
Not fixed. I'm getting this after the upgrade to 5.3.2f1 as well if I try to user Unity Remote !!
FlorianBaptiste
Jan 24, 2016 22:06
The last version of unity is very buggy (5.3.1). First this bug. I don't know what to do but I can't use my project anymore. I am developing an iOS game and it simply crashes everytime I start play mode. PLEASE FIX THIS
Richvon
Jan 24, 2016 11:43
I completely fixed it by re installing the iOS module, running a full build through Xcode, which automatically reimported all of the assets, then the remote worked like it used to. No need to change meta file option.
Rich
ForceVFX
Jan 15, 2016 20:42
I actually fixed it,
seems re starting unity remote 4 & setting meta files as visible, (I think Unity remote was in a frozen state ie, the gyroscope was no longer flipping the logo screen)...the stream, is the "connected" state on Unity Remote 4. once the last reported state 'connected' no longer matches the current state 'frozen' - live memory stream corruption. my guess p-
ForceVFX
Jan 15, 2016 19:04
This is a issue : Unity remote 4, set on recognized IOS device crashes every time...period.
I am two hours in, deleted library...etc...
I am Creating an empty project to submit this a a reproducible bug.
Patrick Force
shmomo
Jan 14, 2016 22:24
Im getting this problem almost daily. I takes 30 min to re-import all assets to fix it. Please re-open this
joshskelton
Jan 13, 2016 15:07
Bump. happened to me today. I can reproduce it, so Hopefully Unity can too.
dre_mcgrail
Jan 12, 2016 11:15
I'm constantly getting this issue in 5.3.1p2 resolved with various work arounds but its happening every 2-10 plays in the editor. Working on an iOS game with 2D sprites and sprite packing, also happening in 3D iOS project while baking light maps.
Hjeldnes
Jan 09, 2016 18:41
I also get it in 5.3.1p2. Happened a lot lately. Deleting library folder makes it go a way for a while. Very frustrating.
slippdouglas
Jan 09, 2016 10:08
I'm seeing it in Unity 5.3.1p2 Personal (latest at time of writing) on OS X 10.8.6. Only happens when the Editor Settings' Unity Remote Device is set to my device (works fine when setting to “None” and relaunching Unity).
Please reopen this issue. People are still hitting this bug and unable to use your product fully because of it. Marking it at “Not Reproducible” when it's clearly not fixed yet is a really dick move. It's understandable that you only have so much time and so many people to fix bugs, but preventing us from voting on this issue is preventing you from understanding what bugs you should be putting time into— time that may including trying a little harder to repro and/or digging in the codebase for the source of the error and trying to work backwards to the fault.
It's becoming more and more common for Unity Tech to get publicly lambasted by game industry experts for the prolific bugs in your software, and the attitude problem you have towards fixing them before shipping or on a reasonable timeframe. Although that's a bigger problem with lots of moving parts, shutting down one of the ways we have to communicate with you is irresponsible and unprofessional. Let's take a step in the right direction and reopen this issue, and other issues where multiple people are still reporting the issue in continually newer versions of Unity. It would really help those of us who are still sticking with your platform to feel like using Unity is not a lost cause.