Search Issue Tracker

Fixed in Unity 2017.1.0f3

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

OSX

-

-

Priority: 2Necessary for shipping a final release

-

Severity: 1Crash or major loss of functionality

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

Comments (7)

  1. 08ff4cb29f62a371225ea5eb6b132034?d=mm

    martingrayson

    Jan 24, 2018 22:32

    Cancel that - wrong bug.

  2. 08ff4cb29f62a371225ea5eb6b132034?d=mm

    martingrayson

    Jan 24, 2018 22:31

    Also seeing this on Windows using both 2018.1.0b3 and 2018.1.0b4

  3. 8139987a7b6bafbe9305d2e594dadf9f?d=mm

    mikaelK

    Jan 22, 2018 17:59

    Me 2018.1.0b3

  4. E881789559ae9c59fc4c2f38241593ac?d=mm

    letonai

    Dec 09, 2017 17:58

    I`ve got the same error on 2017.30f2 on MacOS High Sierra 10.13.2

  5. 36b3c746cd42fa6a4064b859c4626669?d=mm

    richard_heasman

    Sep 01, 2017 10:48

    Still happens for me 2017.2.0b9
    I suspect this only occurs when connected to unity Remote.

  6. 36b3c746cd42fa6a4064b859c4626669?d=mm

    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.

  7. 459d464a0299262ccf03b4564982b8ce?d=mm

    tuannd92_vn

    Jul 26, 2017 17:39

    I got this error 2017.1.0f3, what should i do?

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.