Debug Linux Persona Crash

This post is similar to this with a difference, it only happens if I’m using the Editor in Debug mode (aka. UE4Editor-Linux-Debug).

I don’t know if the crash has the same origin, but from the debug I’ve been doing this is the error message:

Assertion failed: Assertion failed:  [File:/home/ricardo/Programs/UnrealEngine/Engine/Source/Runtime/OpenGLDrv/Private/OpenGLDevice.cpp] [Line: 329]
[API][Error][High][1281] GL_INVALID_VALUE error generated. <numlayers> must be 6 for new texture's target TEXTURE_CUBE_MAP.

I suppose the error occurs while trying to render the Sky Box from the Persona editor.

GDB Backtrace

Crash Log

Hi, no that is a different crash than the linked post. The linked crash was resolved in some commit now merged into 4.15.

Your actual issue is closer to the metal. I would blame the driver, but you provide little detail(and the gdb output is not that helpful either :D) By the way the full crash log from the project is usually more helpful than what debugger gives you.

Also running the editor in Debug mode does produce different results than in the shipping mode.

Where is the crash log located? I’ll reproduce the error and upload the log if it helps. :slight_smile:

I do not have UE here with me but it is in the project directory in the Save subdirectory and it should be quite apparent from there.

I updated the question to have the crash log. Hope it helps.

That’s a valid issue. If you want to fix it quickly, edit OpenGLTexture.cpp, FOpenGLDynamicRHI::RHICreateShaderResourceView() and replace the last parameter in TextureView() - 1 with 6, like shown below.

	FOpenGL::TextureView( Resource, TextureCube->Target, TextureCube->Resource, GLFormat.InternalFormat[bSRGB], MipLevel, 1, 0, 6);

Or just wait until that fix bubbles up to main.

For now I use UE4Editor that doesn’t seem to be affected.

But I can make a Pull Request to correct the issue if it helps.

It has already been fixed in one of development branches, the fix will probably make it to master next week or so.

help my pleas

a) Wrong section of the answer hub

b) possibly wrong product, not sure if we deal with Fortnite here(there might and should be different support channel)

c) you posted to a year old resolved question

d) there is no information in what you are actually reporting(what were you doing while this happened, what are your specs etc.) I am not saying to go post it here now, just for the future.

e) good luck :slight_smile: