Summary: | [radeonsi] Unreal engine 4 Segmentation fault | ||
---|---|---|---|
Product: | Mesa | Reporter: | Iaroslav Andrusyak <pontostroy> |
Component: | Drivers/Gallium/radeonsi | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED MOVED | QA Contact: | Default DRI bug account <dri-devel> |
Severity: | normal | ||
Priority: | medium | CC: | linuxdonald, ttimo |
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Schreenshot1
Screenshot2 |
Description
Iaroslav Andrusyak
2016-03-06 06:18:46 UTC
Looks like UE4Editor overrides some C++ memory allocation APIs, which breaks LLVM. This still happens in current git (dd072cf4b1) with unreal editor 4.16. Kernel 4.12.3-ARCH Rx 480 libdrm-2.4.82 Full log output from two runs. One with default binned2 malloc and one with ansimalloc: https://pastebin.com/tmCAaEkX Created attachment 133122 [details]
Schreenshot1
Created attachment 133123 [details]
Screenshot2
Screenshost are from version 4.17 after the editor startup freezed my desktop. Only mouse worked. Not likely to be a radeon bug, but here is a possible solution for UE4 4.16: 17:18 <@rcl> if 4.16, remove the linker script 17:18 <@rcl> and try again 17:19 <@rcl> drivers aren't siloed from our new/delete and are probably allocating memory through UE, a user program (see LinuxToolChain.cs) If someone can try that and report, that would help. I tested with the current promoted branch (which has the linker script commented out by default). This gives me a complete desktop freeze like Thomas Kowaliczek already reported. The freeze problems are very likely this issue: https://bugs.freedesktop.org/show_bug.cgi?id=101977 I haven't seen this allocator problem in 4.16 with ubuntu 16.x, I suspect it's tied to a clang / libstdc++ / distribution combo. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1229. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.