Search Issue Tracker
Fixed in 2017.1.0f3
Fixed in 2017.1.X, 2017.2.X
Votes
0
Found in
2017.1.0b7
Issue ID
917133
Regression
Yes
[OS X] CheckDisalowAllocation. Allocating memory when it is not allowed to allocate memory
Steps to reproduce:
1. Open user attached project
2. Observe the Allocating memory error
Expected result: allocating memory error should not appear and project should open up on OS X
Reproduced in: 2017.1.0b5, 2017.1.0a6,
Not reproduced in: 5.6.1p2, 5.5.4f1, 2017.1.0a5
Regression since: 2017.1.0a6
Fixed in: 2017.3.0a3
Backported to: 2017.2.0b6
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
- Editor crashes when debugging a for loop
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
martingrayson
Jan 24, 2018 22:32
Cancel that - wrong bug.
martingrayson
Jan 24, 2018 22:31
Also seeing this on Windows using both 2018.1.0b3 and 2018.1.0b4
mikaelK
Jan 22, 2018 17:59
Me 2018.1.0b3
letonai
Dec 09, 2017 17:58
I`ve got the same error on 2017.30f2 on MacOS High Sierra 10.13.2
richard_heasman
Sep 01, 2017 10:48
Still happens for me 2017.2.0b9
I suspect this only occurs when connected to unity Remote.
richard_heasman
Aug 04, 2017 14:40
I had this issue in 5.6.1f1, I have just upgraded to 2017.1.0f3 and it still happens.
100% stops game progress.
tuannd92_vn
Jul 26, 2017 17:39
I got this error 2017.1.0f3, what should i do?