1488 replies to this topic

[sliderpoint]

Crash report VPX rev3618
============
Process: vpinballx.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:0047E084
Attempt to write to 0x04ECF12C
Thread ID: 0x2838 [10296]

Call stack
==========
0047E084 vpinballx.exe (0xFFFFFFFFC041EC48 0x1160F7B0 0x0000000C 0x7667af90)
004E320E vpinballx.exe (0x3CEBB9E1 0x0000000A 0x3DCCCCCD 0x3fb45851)
004E2A77 vpinballx.exe (0x3FB45851 0x004E3E7F 0x0B51EC60 0x1160f7b0)
3DCCCCCD  (0x0B51EC60 0x1160F7B0 0xFFFFFFFFFFFE8E0E 0x005ef33f)
004E3E7F vpinballx.exe (0x00000000 0x7EE65040 0x1160F7B0 0x7ee65040)
3DCCCCCD  (0x04E465F0 0x00000000 0x7667AF90 0x00000007)

Environment
===========
Date/time: 3/2/2019, 15:56:33:985
Number of CPUs: 8
Processor type: 586
System: Windows 10 (10.0 16299)

Memory status
=============
Total Reserved: 343804K (335M) bytes
Total Commited: 2285372K (2231M) bytes
Total Free: 1565064K (1528M) bytes
Largest Free: 1462848K (1428M) bytes

Registers
=========
EAX=04ECED70 EBX=00000000 ECX=11B76510 EDX=0067282C
ESI=11B76510 EDI=8C401AB0 EBP=00000000 ESP=0019F780 EIP=004EA0F9
FLG=00010213 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.
 

-Mike

I've had some various crashes at different times as well as JP described.  copying/pasting with more than one table open at a time.   But I have also had the random crash mid play with latest build from today.  This one (let me know if you want the dump):

[Schlabber34]

Toxie, Fuzzel, thanks for your hard work!

SCHWEINEGEIL!

Gesendet von meinem SM-G955F mit Tapatalk

[jpsalas]

The new revision, 3618, still crashes a lot when quitting a table. I have not played enough to see how it works while playing.

 

But here it is a crash when pressing ESC and Q to stop playing. Just using VPX, no B2S or menu systems.

 

https://app.box.com/...m4068e34978rwra

 

JP

[fuzzel]

Ok thanks for the crash.txt files. I'll check that.

[fuzzel]

rev3623 is up:

 

- fix for the random crashes (hopefully)

- cleanups

[jpsalas]

rev3623 is up:

 

- fix for the random crashes (hopefully)

- cleanups

 

I have tested this revision for a few hours and it has not crashed yet I'll test it more later today, but for now it looks very stable.

[Thalamus]

No issues for me either.

[toxie]

@fuzzel: weird that the recent changes with 2nd device caused this. does not make any sense to me.  :/

[fuzzel]

Well actually it does. Some elements use the second device but with a call to the primary render device. The initialization of both devices weren't 100% the same after the last code changes. I think we let it as is and revisit the code parts after releasing 10.6.

[jpsalas]

The new revision still crashes during playing. It looks like it happens when the ball hits a gate or a trigger, but you never know what the rom was going to start, like flashers or lights. I was playing my version of TOTAN

I guess the dump is very similar to the others. Here it is:

 

Crash report VPX rev3623-while playing.ZIP

 

JP

[Carny_Priest]

rev3623 - player consistently opens on my backglass screen although it is not the primary Windows display. This might be happening with me as a by-product of the way I am currently installing and configuring new tables. 

 

Launch editor while desktop configuration is in 2K with backglass as primary display so that I can actually read scripts and dialogs.

Execute a dc2.exe profile to change to a 4K DSR desktop configuration; switches Windows primary display to playfield.

Launch player - "Play"

 

Prior to rev3623 - table would always display on playfield as it is the primary monitor when I launch the player  

[fuzzel]

The new revision still crashes during playing. It looks like it happens when the ball hits a gate or a trigger, but you never know what the rom was going to start, like flashers or lights. I was playing my version of TOTAN

I guess the dump is very similar to the others. Here it is:

 

Crash report VPX rev3623-while playing.ZIP

 

JP

The call stack points to complete different position in the code. It looks like something went wrong while updating the HitThreshold for hittargets/primitives but it's not really clear to me why that produced a crash. Did you use this new HitThreshold feature in your TOTAN table?

[Draifet]

Today I tried rev 3523 and on some tables i have a lot worse performance than with the last oficial release (Nvidia Gforce 1080TI, 16GB Ram @3200 I7 7700K, Gsync enabled at 240 Hz monitor). Maybe a Gsync problem, but on some tables it works fine (same user options).

[toxie]

rev3623 - player consistently opens on my backglass screen although it is not the primary Windows display. This might be happening with me as a by-product of the way I am currently installing and configuring new tables. 

 

Launch editor while desktop configuration is in 2K with backglass as primary display so that I can actually read scripts and dialogs.

Execute a dc2.exe profile to change to a 4K DSR desktop configuration; switches Windows primary display to playfield.

Launch player - "Play"

 

Prior to rev3623 - table would always display on playfield as it is the primary monitor when I launch the player  

 

New dev Caligula added display selection, which seems to pick a different default than before. You can configure it in the video preferences.

Today I tried rev 3523 and on some tables i have a lot worse performance than with the last oficial release (Nvidia Gforce 1080TI, 16GB Ram @3200 I7 7700K, Gsync enabled at 240 Hz monitor). Maybe a Gsync problem, but on some tables it works fine (same user options).

 

Last official release means 10.5? Also which tables did you test so that i can try to reproduce?

[Caligula_]

@Draifet:Hi, I'm the new coder so don't be to harsh if messed up. It was my first commit ;-) Can you post your settings (VP Settings and your display config)? And does it only happen on the GSync display or on all displays? And can you check if your primary monitor is also the monitor with the number 1 in your windows settings?

Edited by Caligula_, 05 February 2019 - 08:57 PM.

[Carny_Priest]

 

rev3623 - player consistently opens on my backglass screen although it is not the primary Windows display. This might be happening with me as a by-product of the way I am currently installing and configuring new tables. 

 

Launch editor while desktop configuration is in 2K with backglass as primary display so that I can actually read scripts and dialogs.

Execute a dc2.exe profile to change to a 4K DSR desktop configuration; switches Windows primary display to playfield.

Launch player - "Play"

 

Prior to rev3623 - table would always display on playfield as it is the primary monitor when I launch the player  

 

New dev Caligula added display selection, which seems to pick a different default than before. You can configure it in the video preferences.

Today I tried rev 3523 and on some tables i have a lot worse performance than with the last oficial release (Nvidia Gforce 1080TI, 16GB Ram @3200 I7 7700K, Gsync enabled at 240 Hz monitor). Maybe a Gsync problem, but on some tables it works fine (same user options).

 

Last official release means 10.5? Also which tables did you test so that i can try to reproduce?

 

 

Thanks all! Got it figured out.

[jpsalas]

 

The new revision still crashes during playing. It looks like it happens when the ball hits a gate or a trigger, but you never know what the rom was going to start, like flashers or lights. I was playing my version of TOTAN

I guess the dump is very similar to the others. Here it is:

 

Crash report VPX rev3623-while playing.ZIP

 

JP

The call stack points to complete different position in the code. It looks like something went wrong while updating the HitThreshold for hittargets/primitives but it's not really clear to me why that produced a crash. Did you use this new HitThreshold feature in your TOTAN table?

 

No. The table is more or less the same as it was in 2016. None of the primitives is collidable, and it can be played with 10.5.

[sliderpoint]

Another mid play crash:

Crash report VPX rev3623
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:0047E544
Attempt to write to 0x02EBF0AC
Thread ID: 0x3FDC [16348]

Call stack
==========
0047E544 VPinballX.exe (0xFFFFFFFFBFCCA496 0x115FFA50 0x0000000C 0x74076360)
004E370E VPinballX.exe (0x086E6AE0 0x115FFA50 0xFFFFFFFFFFFB4E61 0x00339d8a)
004E437F VPinballX.exe (0x02E202C0 0x00000000 0x74076360 0x00000007)

Environment
===========
Date/time: 6/2/2019, 13:30:09:385
Number of CPUs: 8
Processor type: 586
System: Windows 10 (10.0 17134)

Memory status
=============
Total Reserved: 201448K (196M) bytes
Total Commited: 2288760K (2235M) bytes
Total Free: 1704032K (1664M) bytes
Largest Free: 1602304K (1564M) bytes

Registers
=========
EAX=02EBECF0 EBX=00000000 ECX=7E598A30 EDX=00672D50
ESI=7E598A30 EDI=8C9A3E50 EBP=00000000 ESP=0019F780 EIP=004EA5E9
FLG=00010217 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Mini dump saved successfully.

[Draifet]

@toxie @Caligula_

About stutter/gsync, yes i mean official 1.5, I saw the new display selection on the beta, I have to select 1 as main screen.

I tried FPS cap at 240, mode 0, 1 and 2, but nothing works, if I press F11 I can read +/- 180 FPS, but I have stutter. On the VPX 1.5 i have to put 0 on the table preferences to play it with gsync working fine.

Edited by Draifet, 07 February 2019 - 05:37 PM.

[Rajo Joey]

I also had a crash during play with the new version. :-(
 

Crash report VPX rev3623
============
Process: vpinballx.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:0047B9E5
Attempt to read from 0xFF180404
Thread ID: 0x7E0 [2016]

Call stack
==========
0047B9E5 vpinballx.exe (0x43287730 0x43287880 0x3975D520 0x0000000b)
004E35D6 vpinballx.exe (0x004E437F 0x115E4C60 0x3975D520 0xffffffffffefe455)
3FBF6C72  (0x115E4C60 0x3975D520 0xFFFFFFFFFFEFE455 0x00619d8a)
004E437F vpinballx.exe (0x02F22740 0x00000000 0x73E66360 0x00000007)

Environment
===========
Date/time: 7/2/2019, 22:01:37:402
Number of CPUs: 8
Processor type: 586
System: Windows 10 (10.0 17134)

Memory status
=============
Total Reserved: 345268K (337M) bytes
Total Commited: 1643124K (1604M) bytes
Total Free: 2205848K (2154M) bytes
Largest Free: 2014400K (1967M) bytes

Registers
=========
EAX=FF180400 EBX=43287730 ECX=0019F3DC EDX=40663BD4
ESI=43287880 EDI=40663BD4 EBP=00000000 ESP=0019F780 EIP=004EA5E9
FLG=00010202 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.