Metal bug on nVidia GPU causes editor lock

Development Platform & Builds
, , ,
1

Hi,

Could someone please try the following on Mac with Metal with an nVidia GPU (preferably GTX 700 series):

  1. Create a new project from Blueprint > Vehicle Advanced
  2. After the scene loads, start rapidly scrolling out
    of the scene with the mouse wheel

Sometimes this locks up my editor completely.

When this happens I see the following start appearing on the console:

[2016.01.25-18.41.46:688][309]LogMetal:Error: Command buffer 0x618000295a90 failed!
[2016.01.25-18.41.47:043][314]LogMetal:Error: Command buffer 0x610000485eb0 failed!
[2016.01.25-18.41.47:201][317]LogMetal:Error: Command buffer 0x610000486180 failed!
[2016.01.25-18.41.47:551][323]LogMetal:Error: Command buffer 0x6100004861d0 failed!

After some engine source code modification, where I put a [CommandBuffer waitUntilCompleted]; and CommandBuffer error checking after every [CommandBuffer commit]; invocation, and I get the bug, the error starts being non-null and contains this:

Error Domain=MTLCommandBufferErrorDomain Code=1 "Internal Error (IOAF code 1)" UserInfo={NSLocalizedDescription=Internal Error (IOAF code 1)}

Thank You!

2

Hi,

iMac 14,2 (Late 2013), GTX 775M

3

Hey ,

Are you on a Hackintosh computer? I don’t know of any Apple product with an Nvidia 700 series card. Can you send your specs?

-.

4

Oh, and I could also try this on a MacPro with D300s and I could not reproduce it there.

5

Hi,

Here’s a bit of update. Today a rebuilt the UE4 with debug settings (from branch 4.11) and tried the following:

  • On a hackintosh (Core i7 3770, 32GB
    RAM, GTX 780) I could reproduce the
    bug easily.
  • On the same hackintosh I swapped the
    the GPU to a GTX 760, I could still
    reproduce it BUT it was much harder
    to do.
  • Because of the hard reproducibility I
    went back to the MacPro and tried to
    make it crash (4.11prev-4) but after
    20 minutes it still wouldn’t
  • I don’t have access to the iMac (not
    mine), so I couldn’t retry on that
  • In Xcode I tried to debug, but the
    problem is that I would need to do a
    capture frame on the exact frame
    which would be the first to fail. I
    have no idea if thats even possible.

Hope my little update helps.
-Mac

6

Hey ,

I tracked down our iMac with a 775M and was able to reproduce the issue. It was previously reported on an internal project, but I have entered it for the Editor as UE-26410.

Thanks for reporting your findings on this.

-.

7

Hi!

Any update on this with Preview 8 & OS X 10.11.4?

Thanks,
M.

8

Hey ,

Our machine that reproduced this issue no longer shows the bug as of Preview 8, can you try it out and tell me if you’re still having issues?

-.

9

Hi,

Yeah, it looks like this issue is fixed!

Thanks, M

10

logfile

OK, maybe not. :frowning:

There is a new GPU driver crash resulting from the same “moving around in the scene”. I only played around on the GTX 780 hackintosh, and I have no clue if this is reproducible on any other of prev. reported systems.

OS X 10.11.4 + Preview 8

I just held down the right button and moved around in the scene with WASD, and when I let go of the button, the editor crashed. Could you please check if you could reproduce this or not?

Thanks, M

11

Hey ,

Can you open up a new AnswerHub thread for this as it seems to be a different issue entirely.

-.