All games maded with Unity engine in steam catalog crashes on AMD GPU, but worked on Intel GPU on same machine.

[Marek Olšák]

On Thu, Feb 1, 2018 at 5:27 PM, mikhail <mikhail.v.gavrilov at gmail.com> wrote:
> On Tue, 2018-01-30 at 22:38 +0100, Marek Olšák wrote:
>> On Tue, Jan 30, 2018 at 10:36 PM, Marek Olšák <maraeo at gmail.com>
>> wrote:
>> > On Tue, Jan 30, 2018 at 10:04 PM, mikhail <mikhail.v.gavrilov at gmail
>> > .com> wrote:
>> > > On Tue, 2018-01-30 at 20:12 +0100, Marek Olšák wrote:
>> > > > Can you record an apitrace on a driver that is not radeonsi?
>> > >
>> > > All traces from five listed games was recorded on Intel GPU (not
>> > > radeonsi).
>> > > I also understood why for some games traces was not recorded
>> > > yesterday.
>> > > It happens because such games are 32 bit and for correct working
>> > > apitrace was needed apitrace-libs-7.1-7.fc27.i686 package, but
>> > > only
>> > > apitrace-libs-7.1-7.fc27.x86_64 was installed.
>> > >
>> > > > If yes, can you correctly replay the apitrace on a driver that
>> > > > is not
>> > > > radeonsi?
>> > >
>> > > All traces was correctly replayed on Intel GPU (not radeonsi).
>> > >
>> > > > If yes, can you reproduce the crash if you replay the apitrace
>> > > > on
>> > > > radeonsi?
>> > >
>> > > All traces also was correctly replayed on AMD Vega 56 GPU
>> > > (radeonsi)
>> > > without crashes.
>> > >
>> > > What does this give us?
>> > >
>> > > Anyway launching listed games under AMD Vega 56 GPU lead to new
>> > > crases.
>> >
>> > Thanks. It's possible that Unity contains its own version of LLVM
>> > or
>> > its own version of some standard libraries that LLVM uses, and
>> > radeonsi doesn't like when games replace its dependencies.
>>
>> It's also possible that some symbols exported by Unity clash with
>> those exported by LLVM.
>>
>> Marek
>>
>
> I am created thread in Unity forum with describeb issue and link to
> this thread:
> https://forum.unity.com/threads/all-games-maded-with-unity-engine-crash
> es-on-amd-gpu-but-worked-on-intel-gpu-on-same-machine.515193/#post-3376
> 548
>
> And got answer from Tak:
> This looks like a driver crash in free/delete after
> mesa_glsl_link_shader.
> I don't believe that Unity is duplicating these symbols (as concluded
> in the freedesktop thread) - as far as I can tell, this is all in the
> radeonsi driver.

If it was a Mesa issue, apitrace would reproduce it. It's a crash in
free(), which means something is wrong with the heap. There is no
evidence that Mesa corrupted the heap. The heap might have been
corrupted outside of Mesa.

Can you run one of the games under valgrind?

Marek