Unity 5.4.0b15 "GfxFramebufferGLES: An active RenderTargetSetup has dangling pointers."

Unity Engine
1

Hi all,

I just updated my unity to the beta version, and now I keep getting an error message:
“GfxFramebufferGLES: An active RenderTargetSetup has dangling pointers.”

This error message seems to happen when using Unity Remote, and this didn’t happen with Unity 5.3.
I tried with iPhone 5 and iPhone 6s, but it still happens every time I use Unity Remote.

Everything works perfectly fine, but I’m just wondering what’s causing this error message.

Thanks in advance for your help!

2

We recently had an issue with our lighting camera that was giving this error when we upgraded to 5.3.4p3. Turns out we were assigning the render texture to a global shader variable as well as the target for the camera, and needed to discard and set both to null on destroy.

3

kmckenna, does this imply that it’s fixed? I’m still getting this on 5.4.0f2

4

@kenmgrimm_1 The issue is still active, it’s a regression: Unity Issue Tracker - Unity throws "GfxFramebufferGLES: An active RenderTargetSetup has dangling pointers." while Unity Remote is in use

5

Gotcha, thanks for the update!

6

I get this error on every frame that I use “Application.CaptureScreenshot,” so it’s not only limited to Unity Remote.

7

Any updates on this? I’m still able to run my game with Unity Remote despite this error message, but it’s hogging my console window. God damn!

Anyone found any work arounds? Is there a way to ignore this error in the meantime (I’ve read this is ill-advised)

8

I just ran into this issue this morning with a student. Is there any answer to why this is happening? Would love to find a solution.

9

I get the same error
(see http://forum.unity3d.com/threads/unity-remote-5-controls-not-working-case-830510.430330/ )
Don’t know if it’s related, but additionally, the FPSController + DualTouchControls don’t work properly as explained in that topic.
Do you face the same issue? Or is it just the error messages you get?
@SaraCecilia
Are there any plans on solving this? It’s been discovered more than 4 months ago now.

1 Like
10

I am using Unity Remote 5 and Unity 5.4.1f1 Personal, the issue still repros

11

Same issue as well :frowning:

v5.4.1p2

12

You all might want to submit this as a bug so they know it’s still out there.

13

I solved the DualTouchControls issue by deleting the UI object and dragging a new one from the prefab into the scene.

However, the problem discussed in this topic here still persists.

@Jaimi
Also, the bug is already known for quite some time (for half a year). You can take a look here:

It’s kind of weird, though. When 5.4.1 was new, they said it would be fixed in 5.4.4 (why would they skip 5.4.2 and 5.4.3 ?), then it said the fix is going to be in 5.4.2. But now that 5.4.2 is released, they changed it to fixed in 5.4.3…

14

I don’t know the procedures of the Unity QA group. However, I was informed at one time that bugs needed to be re-reported if they still existed in later versions, as older bugs were moved to lower priority.

1 Like
15

@Jaimi
I see! That’s good to know. But I think in this case, they are aware that the issue persists, because they changed its status to fixed in 5.4.3. So hopefully, this is indeed fixed in 5.4.3 eventually.

16

Any update on this issue? It still persists for me when I am using Unity Remote 5 on my iPhone 6s to run the Space Shooter game tutorial. Dangling Pointers sound serious :open_mouth:

17

Which version of Unity are you on?

I just tried with 5.4.3 and the error is gone, and it should also be fixed in 5.4.2p2