From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94410] [radeonsi] Unreal engine 4 Segmentation fault
Date: Sun, 30 Jul 2017 17:14:46 +0000 [thread overview]
Message-ID: <bug-94410-502-aLxOy6jbuN@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94410-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 549 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=94410
--- Comment #6 from Timothee Besset <ttimo@ttimo.net> ---
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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1351 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-07-30 17:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 6:18 [Bug 94410] [radeonsi] Unreal engine 4 Segmentation fault bugzilla-daemon
2016-03-07 9:30 ` bugzilla-daemon
2017-07-24 19:37 ` bugzilla-daemon
2017-07-29 14:25 ` bugzilla-daemon
2017-07-29 14:25 ` bugzilla-daemon
2017-07-29 14:26 ` bugzilla-daemon
2017-07-30 17:14 ` bugzilla-daemon [this message]
2017-08-07 23:40 ` bugzilla-daemon
2017-08-07 23:42 ` bugzilla-daemon
2019-09-25 17:54 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-94410-502-aLxOy6jbuN@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox