Description

I noticed this after packaging multiple samples projects on Windows for Linux and running them on my Linux machine.

The project exited cleanly, but there was a crash and callstack generated in the terminal window and the process would hang there.

Steps to Reproduce

Repro:

  1. On a Windows machine create a new Blueprints project.
  2. In the editor, package the project for Linux using the Development build configuration.
  3. Transfer the packaged project to a Linux machine.
  4. Modify the <projectname>.sh script in the root folder of the packaged project as executable
  5. Open a terminal window in the root folder of the packaged project
  6. Enter './<projectname>.sh' into the terminal window and press enter to run the project
  7. After the project opens, press ~ to open the command line in the project and type 'Exit' to close the project.
  8. Observe the output in the terminal window

Result:
After the project closes and UE logging ends, there is a crash freeing up memory and the process hangs.

Expected:
Project exits cleanly and a new command line is ready in the terminal window.

Frequency:
100%

Callstack

Signal 11 caught.
Malloc Size=131076 LargeMemoryPoolOffset=131092
CommonLinuxCrashHandler: Signal=11
Malloc Size=65535 LargeMemoryPoolOffset=196655
[2016.08.18-19.04.16:965][134]LogLinux: === Critical error: ===
Unhandled Exception: SIGSEGV: invalid attempt to access memory at address 0x75d80000

[2016.08.18-19.04.16:965][134]LogLinux: Fatal error!

[Callstack] 00 0x0000000001cc3f8f FLinuxPlatformStackWalk::CaptureStackBackTrace(unsigned long long*, unsigned int, void*)
[Callstack] 01 0x0000000001bb98f5 FGenericPlatformStackWalk::StackWalkAndDump(char*, unsigned long, int, void*)
[Callstack] 02 0x0000000001c8b3c1 FLinuxCrashContext::CaptureStackTrace()
[Callstack] 03 0x00000000045b297b CommonLinuxCrashHandler(FGenericCrashContext const&)
[Callstack] 04 0x0000000001c8f61c PlatformCrashHandler(int, siginfo*, void*)
[Callstack] 05 0x00007fde796da3d0 /lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x7fde796da3d0]
[Callstack] 06 0x00007fde78a228a0 /lib/x86_64-linux-gnu/libc.so.6(+0x8e8a0) [0x7fde78a228a0]
[Callstack] 07 0x0000000001c3a0d0 FMallocPoisonProxy::Free(void*)
[Callstack] 08 0x0000000001c33cd1 FAsyncWriter::~FAsyncWriter()
[Callstack] 09 0x0000000001c33d69 FAsyncWriter::~FAsyncWriter()
[Callstack] 10 0x0000000001bfa6ec FOutputDeviceFile::TearDown()
[Callstack] 11 0x0000000001bfa51e FOutputDeviceRedirector::TearDown()
[Callstack] 12 0x0000000001b89e23 FEngineLoop::AppExit()
[Callstack] 13 0x00000000045b3268 CommonLinuxMain(int, char*, int [Image Removed](wchar_t const))
[Callstack] 14 0x00007fde789b4830 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fde789b4830]
[Callstack] 15 0x0000000001b7066c Engine/Binaries/Linux/UE4Game() [0x1b7066c]

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-34909 in the post.

0
Login to Vote

Fixed
ComponentTools
Affects Versions4.13
Target Fix4.13
Fix Commit3097128
Main Commit3109685
Release Commit3097128
CreatedAug 18, 2016
ResolvedAug 22, 2016
UpdatedApr 27, 2018
View Jira Issue