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

On Fri, Feb 2, 2018 at 5:13 PM, mikhail wrote: > On Thu, 2018-02-01 at 21:31 +0100, Marek Olšák wrote: >> >> Valgrind doesn't show any memory-related issue with Mesa. It does show >> an issue with "New Unity Project". This can corrupt the heap and cause >> a random

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

On 2018-02-02 05:13 PM, mikhail wrote: > On Thu, 2018-02-01 at 21:31 +0100, Marek Olšák wrote: >> >> Valgrind doesn't show any memory-related issue with Mesa. It does show >> an issue with "New Unity Project". This can corrupt the heap and cause >> a random crash on the next call of

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

On Thu, 2018-02-01 at 21:31 +0100, Marek Olšák wrote: > > Valgrind doesn't show any memory-related issue with Mesa. It does show > an issue with "New Unity Project". This can corrupt the heap and cause > a random crash on the next call of malloc/free/new/delete: > > ==17721== Mismatched free() /

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

On Thu, Feb 1, 2018 at 7:39 PM, mikhail wrote: > On Thu, 2018-02-01 at 18:34 +0100, Marek Olšák wrote: >> On Thu, Feb 1, 2018 at 5:27 PM, mikhail > > wrote: >> > On Tue, 2018-01-30 at 22:38 +0100, Marek Olšák wrote: >> > > On Tue, Jan

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

On Thu, Feb 1, 2018 at 5:27 PM, mikhail 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 >> wrote: >> > On Tue, Jan 30, 2018 at 10:04 PM, mikhail > > .com>

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

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 > wrote: > > On Tue, Jan 30, 2018 at 10:04 PM, mikhail > .com> wrote: > > > On Tue, 2018-01-30 at 20:12 +0100, Marek Olšák wrote: > > > > Can you

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

On Tue, Jan 30, 2018 at 10:36 PM, Marek Olšák wrote: > On Tue, Jan 30, 2018 at 10:04 PM, mikhail > 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

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

On Tue, Jan 30, 2018 at 10:04 PM, mikhail 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

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

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

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

Launching games with latest llvm and mesa not solve problem. :( Current versions: mesa: 17.4.0-0.18.git32170d8 llvm: 7.0.0-0.1.r322903 /home/mikhail/.local/share/Steam/steamapps/common/Comedy Night/Comedy Night_Data/Mono/x86/libmono.so(+0x8a0b8) [0xebe5c0b8]

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

On Tue, Jan 30, 2018 at 7:08 PM, mikhail wrote: > Launching games with latest llvm and mesa not solve problem. :( > > Current versions: > mesa: 17.4.0-0.18.git32170d8 > llvm: 7.0.0-0.1.r322903 > > /home/mikhail/.local/share/Steam/steamapps/common/Comedy Night/Comedy

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

On Mon, Jan 29, 2018 at 6:51 PM, mikhail wrote: > > May be problem in my LLVM and MESA? > mesa: 17.4.0-0.16.git41c36c4 > llvm: 7.0.0-0.1.r322132 I don't know. > > I am couldn't update it to much newer version cause newer version is > breaks my GNOME desktop. I am

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

May be problem in my LLVM and MESA? mesa: 17.4.0-0.16.git41c36c4 llvm: 7.0.0-0.1.r322132 I am couldn't update it to much newer version cause newer version is breaks my GNOME desktop. I am wrote about it before in this mailing list. On Mon, 2018-01-29 at 18:34 +0100, Marek Olšák wrote: > Neither

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

Neither of your apitraces crashes on my machine. Marek ___ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx

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

[-gpudriverdevsupport (Bcc)] Let's keep this on amd-gfx. It looks like all backtraces crash in free() or operator delete(). I would say it's heap corruption. Can you record an apitrace on a driver that is not radeonsi? Can you correctly replay the apitrace on a driver that is not radeonsi? Can