[Fixed] [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"

Bugs that have been investigated and resolved somehow.

Moderator: GZDoom Developers

Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"

Postby MasterBeavis » Fri Jun 07, 2019 11:43 pm

im just glad you narrowed it down more lol
User avatar
MasterBeavis
 
Joined: 13 May 2019
Operating System: Windows 10/8.1/8 64-bit
Graphics Processor: ATI/AMD with Vulkan Support

Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"

Postby Dwailing » Sat Jun 08, 2019 12:02 am

MasterBeavis wrote:im just glad you narrowed it down more lol


You're the one who got me looking into Display settings, and you were right about it being something in post-processing. I just started trying settings until something broke, lol. You'd probably have gotten there. More than anything I'm glad I was able to corroborate the issue. Would have been bad if this got written off as just a problem with your hardware.
Dwailing
 
Joined: 28 Jun 2017
Discord: 5896
Operating System: Windows 10/8.1/8 64-bit
Graphics Processor: ATI/AMD with Vulkan Support

Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"

Postby Rachael » Sat Jun 08, 2019 12:11 am

Vulkan is disabled on the 32 bit builds, so that's why it doesn't crash. This doesn't really mean anything.
User avatar
Rachael
Webmaster
 
Joined: 13 Jan 2004
Discord: Rachael#3767
Twitch ID: madamerachelle
Github ID: madame-rachelle
Graphics Processor: nVidia with Vulkan support

Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"

Postby MasterBeavis » Sat Jun 08, 2019 12:16 am

Rachael wrote:Vulkan is disabled on the 32 bit builds, so that's why it doesn't crash. This doesn't really mean anything.

Yea we already figured that out lol its Bloom in Post Processing with Vulkan thats causing it
User avatar
MasterBeavis
 
Joined: 13 May 2019
Operating System: Windows 10/8.1/8 64-bit
Graphics Processor: ATI/AMD with Vulkan Support

Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"

Postby dpJudas » Sat Jun 08, 2019 12:18 am

Dwailing wrote:More than anything I'm glad I was able to corroborate the issue

Yes, thanks once again in confirming this bug report. And thanks for narrowing it down the bloom pass and seemingly related to load/save code (save game thumbnail, most likely). It will help figuring out what could be causing it.
dpJudas
 
 
 
Joined: 28 May 2016

Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"

Postby dpJudas » Mon Jun 10, 2019 1:15 am

Okay, I pushed a commit that I think may fix the issue reported here. Please test again with the next nightly build.
dpJudas
 
 
 
Joined: 28 May 2016

Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"

Postby MasterBeavis » Mon Jun 10, 2019 2:47 am

User avatar
MasterBeavis
 
Joined: 13 May 2019
Operating System: Windows 10/8.1/8 64-bit
Graphics Processor: ATI/AMD with Vulkan Support

Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"

Postby dpJudas » Mon Jun 10, 2019 2:52 am

Oh well. I don't have a clue what is causing the crash then.
dpJudas
 
 
 
Joined: 28 May 2016

Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"

Postby _mental_ » Mon Jun 10, 2019 3:33 am

With this fix I managed to reproduce the crash on Vega occasionally. It's somewhere inside vkCmdBeginRenderPass function.
Spoiler: Callstack

It doesn't happen with validation layers enabled though.
_mental_
 
 
 
Joined: 07 Aug 2011

Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"

Postby dpJudas » Mon Jun 10, 2019 2:17 pm

I pushed another commit that may be the source to that BeginRenderPass crash.
dpJudas
 
 
 
Joined: 28 May 2016

Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"

Postby MasterBeavis » Mon Jun 10, 2019 2:22 pm

User avatar
MasterBeavis
 
Joined: 13 May 2019
Operating System: Windows 10/8.1/8 64-bit
Graphics Processor: ATI/AMD with Vulkan Support

Re: [GZDoom 4.1.2] Vulkan Crashes "AMD 400/500 Series"

Postby _mental_ » Tue Jun 11, 2019 1:44 am

Fixed for me as well.
_mental_
 
 
 
Joined: 07 Aug 2011

Previous

Return to Closed Bugs

Who is online

Users browsing this forum: MSN [Bot] and 0 guests