I have tried a few runs with hlsl disabled and so far no crashes. I will update if otherwise.

No.12416

B2K24

Moderator

Mar 3, 2016, 15:44

What's the GPU's of your main rigs and what drivers are installed for them? Also, please attach your mame.ini so we can see with what settings you're running with.

No.12417

Haze

Senior Tester

Mar 3, 2016, 17:34

edited on: Mar 3, 2016, 17:34

sure this isn't a heat problem on your PC? the report / backtrace looks very strange and unexpected, not something I'd expect to just randomly happen.

No.12418

NekoEd

Senior Tester

Mar 3, 2016, 17:44

Changed version to 0.170 to mesh with report body.

No.12420

Darkfalz

Tester

Mar 4, 2016, 06:17

edited on: Mar 4, 2016, 06:21

Intel HD4000 (or 740M) on Laptop, same crash. 980 on main PC. GPU usage is in single digits so it's not overheating. I confirmed this is a hlsl issue for me - I also tried with a fresh, default MAME install and same random crash when hlsl is enabled. There's a thread on emuchat with same crash described.

Not an NVIDIA issue as happens with Intel too.

No.12421

B2K24

Moderator

Mar 4, 2016, 08:15

I played 3rd Strike for over 30 minutes and didn't encounter any problems here. Are you running with cheats enabled? Can you attach or link your mame.ini?

No.12423

Darkfalz

Tester

Mar 4, 2016, 16:12

It's random, I can play for an hour and then it will crash, or it can crash in attract mode after a minute or two. I have cheats enabled but they don't need to be any activated.

Try Final Fight revenge and just leave it running in attract mode. It crashes most of the time for me.

I uploaded my mame.ini

No.12424

B2K24

Moderator

Mar 4, 2016, 18:21

Thanks for providing your mame.ini as this helps to possibly diagnose problems. At first glance I see you have multithreading enabled which could possibly be the cause of this issue. It's been recommended to have that disabled.

I'll continue to run some tests with my setup to see if I can trigger the issue and then copy over your mame.ini to see if this reported issue can be reproduced.

No.12425

B2K24

Moderator

Mar 4, 2016, 22:21

Confirmed. It's the multithreading that causes the crash. I ran with defaulted mame.ini settings only inserting my HLSL settings and perhaps a couple small other things.
Disable the multithreading in mame.ini and you should be good.

I'm unsure how to mark or clean up this report because it's recommend to run with MT disabled.

Someone else help please :)

No.12431

NekoEd

Senior Tester

Mar 5, 2016, 22:09

This should be suspended and linked to the catchall bug for multithreading issues. I'll take care of that.

No.12434

B2K24

Moderator

Mar 6, 2016, 09:46

Thank you Ed.

No.12437

Darkfalz

Tester

Mar 7, 2016, 05:17

Seems to be a combination of both HLSL and multithreading but as I understanding it most of MAME multithreading is putting the video render under a separate thread so I suppose it shouldn't be too surprising.

I am 99% sure it was stable as of 0.169 though? I never had these crashes before and have had MT on for the last few years.

No.12438

NekoEd

Senior Tester

Mar 7, 2016, 16:19

MAME's multithreading has been getting progressively more and more broken, unfortunately. This is likely just part of the decline. The entirety of the multithreading code seems to need a major revisit/rewrite.

No.12439

Tafoid

Administrator

Mar 7, 2016, 20:38

With the eventual progression of BGFX as the primary video driver which I'm told has MT type behavior built into it - -mt will likely be done away with as an option sooner or later.