Tutorials vs. Bumblebee vs. nVidia

anonymous_user_03b6f6f7 · September 8, 2015, 11:37am

I built the 4.9.0 release branch last night on a 15.04 VM, and am testing it in Ubuntu 15.10 this morning.

I’ve seen the following when testing against the nVidia 670MX chipset (w/355.06 drivers) via Bumblebee, but not when using the Intel HD4000 chipset. I realize this could be due to a bug in UE, the nVidia driver, Bumblebee/primusrun, or even something else… I just thought I’d mention it here for the benefit of the other users. Falling back to Intel graphics for the tutorial seems like an acceptable workaround in the meantime. I’m not sure if using nvidia-prime produces the same results.

Anyway: Even though the “first time” tutorials may start/work normally after creating a project, the UE editor will hard-crash with the following error if I go back at a later time and try to open any specific tutorial:

[2015.09.08-10.51.50:213][769]LogSlate:Warning: Slate: Had to block on waiting for a draw buffer
X Error of failed request:  BadDrawable (invalid Pixmap or Window parameter)                                                 
  Major opcode of failed request:  153 (DRI2)                                                                                
  Minor opcode of failed request:  8 (DRI2SwapBuffers           )                                                            
  Resource id in failed request:  0x4a00044                                                                                  
  Serial number of failed request:  1497                                                                                     
  Current serial number in output stream:  1498                                                                              
Assertion failed: IsInRenderingThread() [File:/home/evil/src_archive/UnrealEngine.release/Engine/Source/Runtime/RenderCore/Private/RenderResource.cpp] [Line: 40]

UE4Editor might want to catch this more gracefully and just abort the operation.

anonymous_user_2b03d27c · September 8, 2015, 1:39pm

Hey 3vi1-

I just want to make sure that I’m following you correctly. The error that you’re reporting is a crash when trying to access tutorials through the editor, correct?

anonymous_user_03b6f6f7 · September 8, 2015, 9:02pm

That’s correct. I’ve not seen any similar crashes running games with primus/nvidia on this system, only with the UE editor.

anonymous_user_2b03d27c · September 9, 2015, 4:19pm

Hey 3vi1-

Does the crash occur when you click on the graduation cap to open the tutorials window or when selecting Help->Tutorials or does it crash when selecting a specific tutorial to play? Simply opening a tutorial did not cause any crash for me. If you can reproduce the crash in a fresh project with no additional content can you post the steps you took that caused the crash?

Cheers

anonymous_user_03b6f6f7 · September 9, 2015, 5:52pm

The crash only occurs after selecting a tutorial. Here’s the steps to reproduce:

Create new blank project.
Click the graduation cap.
Click the drop-down arrow on the top-right and choose “more tutorials”.
Click Blueprints from the list.
Click any of the listed blueprints tutorials. Every so often, one will work, but most will throw the same IsInRenderingThread() assertion:

[2015.09.09-17.42.40:882][ 16]LogSlate:Warning: Slate: Had to block on waiting for a draw buffer
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 153 (DRI2)
Minor opcode of failed request: 7 (DRI2GetBuffersWithFormat )
Resource id in failed request: 0x6000048
Serial number of failed request: 450
Current serial number in output stream: 450
Assertion failed: IsInRenderingThread() [File:/home/evil/src/UnrealEngine_4.9/Engine/Source/Runtime/RenderCore/Private/RenderResource.cpp] [Line: 40]

anonymous_user_03b6f6f7 · September 9, 2015, 5:55pm

[note: If you use primusrun and are creating a new project, the editor will usually crash the same way right after the it creates the project]:

[2015.09.09-17.25.06:124][242]LogGameProjectGeneration: Created new project with 4 files (plus project files)
    X Error of failed request:  BadDrawable (invalid Pixmap or Window parameter)
      Major opcode of failed request:  153 (DRI2)
      Minor opcode of failed request:  7 (DRI2GetBuffersWithFormat  )
      Resource id in failed request:  0x6000044
      Serial number of failed request:  36
      Current serial number in output stream:  36
    [2015.09.09-17.25.06:135][243]Cmd: CLOSE_SLATE_MAINFRAME
    Assertion failed: IsInRenderingThread() [File:/home/evil/src/UnrealEngine_4.9/Engine/Source/Runtime/RenderCore/Private/RenderResource.cpp] [Line: 40] 
    
    Signal 11 caught.
    EngineCrashHandler: Signal=11
    [2015.09.09-17.25.06:144][243]LogLinux:Error: appError called: Assertion failed: Assertion failed: IsInRenderingThread() [File:/home/evil/src/UnrealEngine_4.9/Engine/Source/Runtime/RenderCore/Private/RenderResource.cpp] [Line: 40]

anonymous_user_2b03d27c · September 15, 2015, 6:10pm

Hey 3vi1-

I have not been able to reproduce this issue on my end, possible due to it possibly being a Bumblebee-related issue. Do you have the same problems with tutorial if you use the Intel chipset via Bumblebee or using the nVidia chipset without it?

Cheers

anonymous_user_03b6f6f7 · September 19, 2015, 3:31pm

You can’t really ‘use’ the Intel chipset /via/ Bumblebee; Bumblebee is used to copy frames from a separate X server running on the nVidia chipset to the Intel space. It’s doubtful that the bug is with Bumblebee, because as far as the UE editor is concerned, it’s just running on the nVidia chipset. I’ve never seen another application that will run on the nVidia chipset, but not via Bumblebee.

But, in the interest of being thorough, I’ll install nvidia-prime, and will see if I can reproduce the error when running without Bumblebee in the mix.

anonymous_user_03b6f6f7 · September 19, 2015, 4:17pm

Wow… much to my surprise, it does seem to be somehow directly related to bumblebee/primus. Initial testing via primus-run does not seem to exhibit the same problem. I did not expect that, given my prior experience of running literally over a hundred games with bumblebee without issue.

You can close this and we’ll chalk it up to an incompatibility with Bumblebee - which I’m sure isn’t a priority for you guys to support, since it’s a laptop thing and most of your users would be developing from workstations.

Thanks for taking the time to help me troubleshoot!