4027 replies to this topic

[QuickSave80]

Ever since I upgraded to the newest beta (rev270) i have a weird issue on some tables. After I play a game my buttons all stop working. I can't add credits or start a game. I have to back out and relaunch the table. Once again I get one game that works fine. So far it's happening on Cheech and Chong and Sar trek TNG. I am sure there are more tables, but I only tested 5 or 6. Any ideas what's causing this?

[wiesshund]

Ever since I upgraded to the newest beta (rev270) i have a weird issue on some tables. After I play a game my buttons all stop working. I can't add credits or start a game. I have to back out and relaunch the table. Once again I get one game that works fine. So far it's happening on Cheech and Chong and Sar trek TNG. I am sure there are more tables, but I only tested 5 or 6. Any ideas what's causing this?

 

Dont know if it will make any difference for you, but the latest revision is 10.7.0 rev286

You might try that and see

[naboodiver]

Since installing rev. 270, Batman 66 will no longer exit (PupDisplay.exe continues to run) when I exit through PinballX.    I don't know why.      It will exit ok if I do not use the frontend to launch it.     Anyone else seeing this

[BrandonLaw]

Since installing rev. 270, Batman 66 will no longer exit (PupDisplay.exe continues to run) when I exit through PinballX.    I don't know why.      It will exit ok if I do not use the frontend to launch it.     Anyone else seeing this

 

Mine also started acting wonky in this way once or twice.

 

Looking for that 286boi.

 

@wiesshund ... what magic space did you find that rev?  I did a 1 'goog' and 2 sites.  I'm done.  Hand it over.

Edited by BrandonLaw, 25 July 2021 - 11:18 PM.

[wiesshund]

 

 

 

@wiesshund ... what magic space did you find that rev?  I did a 1 'goog' and 2 sites.  I'm done.  Hand it over.

 

 

I do not know if it will address his issue, as i dont know if its a beta bug he is having, or the beta and something else in his system having a disagreement

but you can always find the latest build here

Actions · vpinball/vpinball (github.com)

 

You click on the latest action, and it gives you the download links for that build/revision

 

It's github, so it will make you make an account if you have not, github always does for areas aside from release sections

but thats ok, as you can use the same account for pulling down latest builds of vpinmame or freezy's or flexDMD etc
you can even have appveyor (what freezy uses) just login with your github.

 

And github never emails you diddly, unless you flag something to be watched or are participating in a bug report.

[BrandonLaw]

Cool thanks brother.  I was there earlier and only still had seen 270.  Really gotta dig.

[batch]

Perhaps I never noticed it before, when I close a table, camera settings remain shown in Properties (I use VPX_7_beta_rev270_rc)

 

[clyde]

I just tried the new beta 10.7 rev.286 from github earlier & every table I tried to open just crashes back to desktop. Anyone else experience this? 

[jpsalas]

I just tried the new beta 10.7 rev.286 from github earlier & every table I tried to open just crashes back to desktop. Anyone else experience this? 

 

Yes, the same with me. Just now version 270 is quiet stable. All the other versions after 270  give an error when trying to load or run a table. I guess they are a "work in progress". 

[wiesshund]

 

I just tried the new beta 10.7 rev.286 from github earlier & every table I tried to open just crashes back to desktop. Anyone else experience this? 

 

Yes, the same with me. Just now version 270 is quiet stable. All the other versions after 270  give an error when trying to load or run a table. I guess they are a "work in progress". 

 

 

WHat is the error?

[jpsalas]

This is what I get:

 

 

Crash report VPX rev286 (f600574)

============

Process: VPinballX.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:004F45F9

Attempt to read from 0x00000000

Thread ID: 0x1E94 [7828]

 

Call stack

==========

004F45F9 VPinballX.exe Primitive::LoadToken + 0x7C9 primitive.cpp(1555+0009 byte(s)) (0x03440000 0x00000000 0x0000088B 0x00000010)

005FFCAE VPinballX.exe std::`dynamic atexit destructor for 'initlocks'' + 0xAC3C6 (0x00000878 0x00000005 0x0000000F 0x79616c00)

005B95BE VPinballX.exe std::`dynamic atexit destructor for 'initlocks'' + 0x65CD6 (0xFFFFFFFF8007000E 0x005711F2 0x034C8040 0x0019f9bc)

005711F2 VPinballX.exe std::`dynamic atexit destructor for 'initlocks'' + 0x1D90A (0x0019F35C 0x0019F9BC 0x0019ED7C 0x034c8040)

005700F7 VPinballX.exe std::`dynamic atexit destructor for 'initlocks'' + 0x1C80F (0x0019F35C 0x0019F35C 0x00001389 0x00000000)

005CD10C VPinballX.exe std::`dynamic atexit destructor for 'initlocks'' + 0x79824 (0xFFFFFFFFDCBAABCD 0x00000000 0x005CBB69 0x034b4e18)

005CBB69 VPinballX.exe std::`dynamic atexit destructor for 'initlocks'' + 0x78281 (0x00001389 0x00000000 0x00000111 0x0019f35c)

005D0010 VPinballX.exe std::`dynamic atexit destructor for 'initlocks'' + 0x7C728 (0x00000111 0x00001389 0x00000000 0x00000111)

005D769D VPinballX.exe std::`dynamic atexit destructor for 'initlocks'' + 0x83DB5 (0x00428AA0 0x000B0658 0x00000111 0x00001389)

77A15E7A user32.dll GetClassLongW + 0x7AA (0x00428AA0 0x00000000 0x00000111 0x00001389)

77A13BEA user32.dll DispatchMessageW + 0x24A (0x779FDE80 0x005CEC86 0x0019F22C 0x00000000)

77A05D70 user32.dll DispatchMessageA + 0x10 (0x0019F22C 0x00000000 0x00000001 0x0019f248)

005CEC86 VPinballX.exe std::`dynamic atexit destructor for 'initlocks'' + 0x7B39E (0x00000000 0x00000001 0x003D4000 0x00759d00)

005BB190 VPinballX.exe std::`dynamic atexit destructor for 'initlocks'' + 0x678A8 (0x00400000 0x00000000 0x03443752 0x00000001)

005E8566 VPinballX.exe std::`dynamic atexit destructor for 'initlocks'' + 0x94C7E (0x003D4000 0x75C0FA10 0x0019FFDC 0x77d47a7e)

75C0FA29 KERNEL32.DLL BaseThreadInitThunk + 0x19 (0x003D4000 0x59110E72 0x00000000 0x00000000)

77D47A7E ntdll.dll RtlGetAppContainerNamedObjectPath + 0x11E (0xFFFFFFFFFFFFFFFF 0x77D68A1E 0x00000000 0x00000000)

77D47A4E ntd

Environment

===========

Date/time: 26/7/2021, 13:08:51:446

Number of CPUs: 16

Processor type: 586

System: Windows 10 (10.0 19043)

 

Memory status

=============

Total Reserved: 64576K (63M) bytes

Total Commited: 174368K (170M) bytes

Total Free: 3955296K (3862M) bytes

Largest Free: 2095472K (2046M) bytes

 

Registers

=========

EAX=00000000 EBX=00000001 ECX=00000000 EDX=0019E98C

ESI=0019E984 EDI=0019EA98 EBP=0019FFEC ESP=0019FFE4 EIP=77D47A4E

FLG=00210282 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B

 

 

Failed to save minidump.

[wiesshund]

@JPSalas

 

Funky, i wonder what the heck it is all angry about there?
Maybe @Toxie will know?

Wonder what i have going on that is different?

 

and NO laughing at my lack of chimichangas!!!

 

Edited by wiesshund, 26 July 2021 - 06:04 PM.

[QuickSave80]

 

Ever since I upgraded to the newest beta (rev270) i have a weird issue on some tables. After I play a game my buttons all stop working. I can't add credits or start a game. I have to back out and relaunch the table. Once again I get one game that works fine. So far it's happening on Cheech and Chong and Sar trek TNG. I am sure there are more tables, but I only tested 5 or 6. Any ideas what's causing this?

 

Dont know if it will make any difference for you, but the latest revision is 10.7.0 rev286

You might try that and see

 

I tried to update to the latest beta but it kept crashing on my system. I had to go back to 270.

[jsm174]

Nothing changed between 270 and 271 (except for a comment)

Diff: https://github.com/v...f653..fb735a420

 

So I would hope 271 works.

 

 

As for 272 - 286, PR #19 was merged

I wonder if something is going on with that.. 

 

Diff: https://github.com/v...f653..f60057463

Edited by jsm174, 26 July 2021 - 06:31 PM.

[DuMichAuch]

Nothing changed between 270 and 271 (except for a comment)

Diff: https://github.com/v...f653..fb735a420

 

So I would hope 271 works.

 Yepp,, 271 is the last build for me without chrashing. Any newer build chrashes while opening tables.

[wiesshund]

 

Nothing changed between 270 and 271 (except for a comment)

Diff: https://github.com/v...f653..fb735a420

 

So I would hope 271 works.

 Yepp,, 271 is the last build for me without chrashing. Any newer build chrashes while opening tables.

 

 

You get same crash log JP has?

 

Wonder why it is crashing?
I have it on 3 dissimilar PC's without issue
 

[DuMichAuch]

VPinballX-10.7.0-286-f600574-win-x86:

Crash report VPX rev286 (f600574)
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:004F45F9
Attempt to read from 0x00000000
Thread ID: 0x22D0 [8912]

Call stack
==========
004F45F9 VPinballX.exe (0x035341C0 0x0350335C 0x03533930 0x0000159c)
0054C435 VPinballX.exe (0xFFFFFFFF8007000E 0x005711F2 0x03503340 0x0019f9bc)
005711F2 VPinballX.exe (0x0019F35C 0x0019F9BC 0x0019ED7C 0x03503340)
005700F7 VPinballX.exe (0x0019F35C 0x0019F35C 0x0000138D 0x00000000)
005CD10C VPinballX.exe (0x0019F030 0x00000000 0x005CBB69 0x03505de8)
005CBB69 VPinballX.exe (0x0000138D 0x00000000 0x00000111 0x0019f35c)
005D0010 VPinballX.exe (0x00000111 0x0000138D 0x00000000 0x00000111)
005D769D VPinballX.exe (0x00428AA0 0x00320F3A 0x00000111 0x0000138d)
76B55E7A user32.dll GetClassLongW + 0x7AA (0x00428AA0 0x00000000 0x00000111 0x0000138d)
76B53BEA user32.dll DispatchMessageW + 0x24A (0x76B3DE80 0x005CEC86 0x0019F22C 0x00000000)
76B45D70 user32.dll DispatchMessageA + 0x10 (0x0019F22C 0x00000000 0x00000001 0x0019f248)
005CEC86 VPinballX.exe (0x00000000 0x00000001 0x003E3000 0x00759d00)
005BB190 VPinballX.exe (0x00400000 0x00000000 0x034845D3 0x00000001)
005E8566 VPinballX.exe (0x003E3000 0x7513FA10 0x0019FFDC 0x772d7a7e)
7513FA29 KERNEL32.DLL BaseThreadInitThunk + 0x19 (0x003E3000 0x25C4B841 0x00000000 0x00000000)
772D7A7E ntdll.dll RtlGetAppContainerNamedObjectPath + 0x11E (0xFFFFFFFFFFFFFFFF 0x772F8A14 0x00000000 0x00000000)
772D7A4E ntdll.dll RtlGetAppContainerNamedObjectPath + 0xEE (0x03106590 0x003E3000 0x00000000 0x78746341)

Environment
===========
Date/time: 26/7/2021, 21:06:29:451
Number of CPUs: 4
Processor type: 586
System: Windows 10 (10.0 19043)

Memory status
=============
Total Reserved: 50152K (48M) bytes
Total Commited: 149972K (146M) bytes
Total Free: 3994116K (3900M) bytes
Largest Free: 2095440K (2046M) bytes

Registers
=========
EAX=00000000 EBX=0019EAA0 ECX=00000000 EDX=0019E98C
ESI=035343F8 EDI=035341C0 EBP=0019FFEC ESP=0019FFE4 EIP=772D7A4E
FLG=00010282 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Mini dump saved successfully.

[wiesshund]

 

VPinballX-10.7.0-286-f600574-win-x86:

Crash report VPX rev286 (f600574)
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:004F45F9
Attempt to read from 0x00000000
Thread ID: 0x22D0 [8912]

Call stack
==========
004F45F9 VPinballX.exe (0x035341C0 0x0350335C 0x03533930 0x0000159c)
0054C435 VPinballX.exe (0xFFFFFFFF8007000E 0x005711F2 0x03503340 0x0019f9bc)
005711F2 VPinballX.exe (0x0019F35C 0x0019F9BC 0x0019ED7C 0x03503340)
005700F7 VPinballX.exe (0x0019F35C 0x0019F35C 0x0000138D 0x00000000)
005CD10C VPinballX.exe (0x0019F030 0x00000000 0x005CBB69 0x03505de8)
005CBB69 VPinballX.exe (0x0000138D 0x00000000 0x00000111 0x0019f35c)
005D0010 VPinballX.exe (0x00000111 0x0000138D 0x00000000 0x00000111)
005D769D VPinballX.exe (0x00428AA0 0x00320F3A 0x00000111 0x0000138d)
76B55E7A user32.dll GetClassLongW + 0x7AA (0x00428AA0 0x00000000 0x00000111 0x0000138d)
76B53BEA user32.dll DispatchMessageW + 0x24A (0x76B3DE80 0x005CEC86 0x0019F22C 0x00000000)
76B45D70 user32.dll DispatchMessageA + 0x10 (0x0019F22C 0x00000000 0x00000001 0x0019f248)
005CEC86 VPinballX.exe (0x00000000 0x00000001 0x003E3000 0x00759d00)
005BB190 VPinballX.exe (0x00400000 0x00000000 0x034845D3 0x00000001)
005E8566 VPinballX.exe (0x003E3000 0x7513FA10 0x0019FFDC 0x772d7a7e)
7513FA29 KERNEL32.DLL BaseThreadInitThunk + 0x19 (0x003E3000 0x25C4B841 0x00000000 0x00000000)
772D7A7E ntdll.dll RtlGetAppContainerNamedObjectPath + 0x11E (0xFFFFFFFFFFFFFFFF 0x772F8A14 0x00000000 0x00000000)
772D7A4E ntdll.dll RtlGetAppContainerNamedObjectPath + 0xEE (0x03106590 0x003E3000 0x00000000 0x78746341)

Environment
===========
Date/time: 26/7/2021, 21:06:29:451
Number of CPUs: 4
Processor type: 586
System: Windows 10 (10.0 19043)

Memory status
=============
Total Reserved: 50152K (48M) bytes
Total Commited: 149972K (146M) bytes
Total Free: 3994116K (3900M) bytes
Largest Free: 2095440K (2046M) bytes

Registers
=========
EAX=00000000 EBX=0019EAA0 ECX=00000000 EDX=0019E98C
ESI=035343F8 EDI=035341C0 EBP=0019FFEC ESP=0019FFE4 EIP=772D7A4E
FLG=00010282 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Mini dump saved successfully.

 

Same crash cause as JP's i think

 

GetAppContainerNamedObjectPath function in both

[jsm174]

I just put a debug build here if anyone wants to try..

 

https://github.com/j...runs/1068707264

 

Maybe we will get a little better stack trace.

[DuMichAuch]

VPinballX-10.7.0-287-077370d-win-x86

Crash report VPX rev287 (077370d)
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:00BBF8E3
Attempt to read from 0x00000000
Thread ID: 0x1ED4 [7892]

Call stack
==========
00BBF8E3 VPinballX.exe (0x045EFCC0 0x0058E6A0 0x0058E434 0xffffffffcccccccc)
00BBF015 VPinballX.exe (0x045EF4A4 0xFFFFFFFFE9346403 0x0058EA4C 0x0058eba0)
00C6527A VPinballX.exe (0xFFFFFFFFE9346463 0x0058EBA0 0x045EF400 0x0058e70c)
00CAD116 VPinballX.exe (0x00000000 0xFFFFFFFFE93465B7 0x0058EA4C 0x0058eba0)
00CB4B7C VPinballX.exe (0x045BF48C 0xFFFFFFFFE93465E3 0x0058EBA0 0xffffffffcccccccc)
00C5E6B0 VPinballX.exe (0x0058F1C8 0xFFFFFFFFE93468F7 0x0058EB64 0x0058eba0)
00D8B9B7 VPinballX.exe (0x045C0728 0x00000001 0x00000005 0x0058f1c8)
00D88DFF VPinballX.exe (0x0000138D 0xFFFFFFFFE93469DF 0x0058EDF8 0x0058eba0)
00D8ABA3 VPinballX.exe (0x0000138D 0x00000000 0x0058EBA0 0x00cccccc)
00D8E6D5 VPinballX.exe (0x0000138D 0x00000000 0xFFFFFFFFE9346CAB 0x00000111)
007C9CA5 VPinballX.exe (0x00000111 0x0000138D 0x00000000 0x0058ee7c)
00DB7305 VPinballX.exe (0x00000111 0x0000138D 0x00000000 0x0058ee7c)
00DB77CC VPinballX.exe (0x00000111 0x0000138D 0x00000000 0x0058ee7c)
00DB761C VPinballX.exe (0x00000111 0x0000138D 0x00000000 0x0058eea8)
00D8E914 VPinballX.exe (0x00000111 0x0000138D 0x00000000 0x001012ce)
007C963D VPinballX.exe (0x001012CE 0x00000111 0x0000138D 0x00000000)
76B5EEBB USER32.dll AddClipboardFormatListener + 0x4B (0x00733EBC 0x001012CE 0x00000111 0x0000138d)
76B55E7A USER32.dll GetClassLongW + 0x7AA (0x00733EBC 0x00000000 0x00000111 0x0000138d)
76B53BEA USER32.dll DispatchMessageW + 0x24A (0x0058F084 0x00D8C999 0x0058F060 0x0058fd84)
76B45D70 USER32.dll DispatchMessageA + 0x10 (0x0058F060 0x0058FD84 0x007215A0 0xffffffffcccccccc)
00D8C999 VPinballX.exe (0x007215A0 0x0058F0C8 0x0058FD94 0x00d66cca)
00D84174 VPinballX.exe (0xFFFFFFFFE9347F3B 0x007215A0 0x007215A0 0x0030d000)
00D66CCA VPinballX.exe (0x00720000 0x00000000 0x04534693 0x00000001)
00E0054D VPinballX.exe (0xFFFFFFFFE9347CBF 0x007215A0 0x007215A0 0x0030d000)
00E003D7 VPinballX.exe (0x0058FE20 0x00E005C8 0x0058FE30 0x7513fa29)
00E0026D VPinballX.exe (0x0058FE30 0x7513FA29 0x0030D000 0x7513fa10)
00E005C8 VPinballX.ex7513FA29 KERNEL32.D772D7A7E ntdll.ntdll.dl
Environment
===========
Date/time: 26/7/2021, 21:55:06:885
Number of CPUs: 4
Processor type: 586
System: Windows 10 (10.0 19043)

Memory status
=============
Total Reserved: 48428K (47M) bytes
Total Commited: 166744K (162M) bytes
Total Free: 3979068K (3885M) bytes
Largest Free: 2082256K (2033M) bytes

Registers
=========
EAX=00000000 EBX=00733EBC ECX=045EFCC0 EDX=00000000
ESI=0058E340 EDI=0058E380 EBP=0058FE9C ESP=0058FE94 EIP=772D7A4E
FLG=00010282 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Mini dump saved successfully.