Search Issue Tracker

Fixed in Unity 5.4.0

Votes

33

Found in

5.4.0a5

Issue ID

750405

Regression

No

[OSX] RenderSurface attachment asserts on various projects, in 5.4 beta builds

Shaders

-

-

Priority: 2Necessary for shipping a final release

-

Severity: 0Severity not yet defined

Steps to reproduce:

1. Open Unity;
2. Open attached project;
3. Open "1.unity" scene;

4. Notice that there are 3 planes in the scene with 3 different Shaders having uniform arrays parameters and script, processing those parameters at runtime;
5. Enter Play mode;
6. Zoom in/Zoom out by scrolling mouse wheel in the Scene view;
7. Wait for some time (10-20 seconds).

Actual result:
Weird errors appear in the console:

attach.color[0]->backBuffer == attach.depth->backBuffer
!attach.color[0] || !attach.color[0]->backBuffer

See attached actual.png screenshot.

Notes:
- Reproduces only on OSX (10.11.4), OpenGL4.1 (GLCore) mode;
- Doesn't reproduce on Windows 10;
- The issue doesn't reproduce every time;
- The other possible symptom of this failure is that Game View becomes unresponsive and following assertions appear (in addition to abovementioned ones):

!::HasAsAttachment(GLESRenderTargetSetup(m_PendingFramebuffer), rbid)

!::HasAsAttachment(GLESRenderTargetSetup(m_CurrentFramebuffer), rbid)

Comments (37)

  1. B4163e2bfc9148aca54e20d4bcfccc7b?d=mm

    jmitcheson

    Aug 19, 2016 00:05

    I'm considering switching to Windows because apparently this is never going to be fixed? 5.4.0f1 - happens about 50% of the time I run my project. I use the reset workspace menu item about 50 times a day :(

  2. 76356cef93c14c2e020d42acf803538b?d=mm

    dizzlebomb

    Jul 20, 2016 19:23

    Just got this on OSX with 5.4.0f1, will look into some of the above comments.

  3. 7e5af95ee19765e6259883c1ac73fe81?d=mm

    ashwinFEC

    Jul 19, 2016 08:59

    Not fixed still happens in RC1

  4. Ff3307d7503616c348506722f9c074cf?d=mm

    WilB

    Jul 16, 2016 12:21

    @FF1878 setting the IDE layout to Default definitely solved the problem for me. OSX. Unity 5.4.0b22.

  5. B9516e2dcb7f8742732fd674b4dc12a7?d=mm

    Voronoi

    Jul 11, 2016 22:13

    Still in 5.4.0b25

  6. B9516e2dcb7f8742732fd674b4dc12a7?d=mm

    Voronoi

    Jul 11, 2016 22:07

    Still seeing this in 5.4b25. Really annoying and hard to keep working on a project with this happening so frequently. I can confirm it does not happen on Windows, where I just finished up a project.

  7. Ecee9cdb7924eb19d2179a9871462a87?d=mm

    rmb303

    Jul 11, 2016 20:54

    It's still present in 5.4.0b25 too.
    It just suddenly appears randomly.
    I might not get it for days, then one day it just pops up again.
    Quitting makes it go away, but it sometimes comes back.

  8. F80d2e987fc86920d445859632db3f9e?d=mm

    GilCat

    Jul 04, 2016 16:59

    Still present on b24. How can this go for so long?

  9. 5144bfe7881f7e1316f285fc9d2062cd?d=mm

    Enrico-Monese

    Jun 30, 2016 14:14

    Still present in b23

  10. 5144bfe7881f7e1316f285fc9d2062cd?d=mm

    Enrico-Monese

    Jun 28, 2016 14:39

    Nope wasn't the Graphics jobs. Actually just changing one thing in the Player Settings fixes it for one time. You play it and it works, play again and it's broken again. But if you change something in the settings then you have another round without errors.
    This is strange

All about bugs

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