Jump to content

All my products and services are free. All my costs are met by donations I receive from my users. If you enjoy using any of my products, please donate to support me. My bare hosting costs are currently not met so please consider donating by either clicking this text or the Patreon link on the right.

Patreon

Recommended Posts

Posted
1 hour ago, Tom Speirs said:

Ill check. Can't say i see that behaviour. Just a thought. I wonder if its the script launched on exit?

Happy new year Tom.

I will try without the end script. It is for setting the screem to portrait mode and set the correct resolutions on all screens

Posted

You are right Tom.
A command in the batch file is causing that PinballX will not close 
I use this batch file for the core and the legacy version.
The batch file is executing and exiting correctly, but PinballX process is still present.

This is the batch file and PinballX won't close after something is done with the Screen

c:\windows\system32\reg.exe import C:\Pinball\scripts\DisplayTools\DC2\monitor_200dpi.reg
C:\Pinball\scripts\DisplayTools\dc\dc64cmd.exe -rotate=right

I tried another program as well (DC2.exe) , but changing something to the display makes PBX still running.

if I set "Wait for exit" to NO, all is working (And batch file is Setting the correct entries as well, so do not spend a lot of time on it.

EDITEven with wait for exit no, it will keep the process alive.
Adding a timeout before the display must change and setting the  "wait for exit"  to no, close PinballX. 
It looks like that when the screen changes I quit PBX, the process cannot release something and will stay alive. 
I will try to do a procmon and processExplorer to check what is keeping the process alive

EDIT 2: Not sure if this helps :
The follwowing threads still consumin CPU when PBX closed

image.thumb.png.444dbd002cbdad77a2a4e773fdb36dd0.png

According to Procmon, it is creating new threads as well and closes them :
image.thumb.png.f42ee67ff24a84103c34cd86ec04871a.png

But not able to match the thread ID's that are created and are still in use ...

Suspending the 3 threads, will Show no more activity of PinballX (no CPU activity , and no more threads to create/exit)

  • 2 weeks later...
Posted
19 hours ago, Tom Speirs said:

Please try 5.35 and let me know.

It's getting worse for me.

Quiting PBX noe leaves a part of the backglass on the screen, and that process is still active:

image.thumb.png.1a1d5b8d04584ec54cd56784f29b7bfa.png

 

log is not showing anything specials

Process explorer shows the following threads are still active:

image.thumb.png.fca1206f199742ee0d524b6da771d7fa.png

log.txt

Posted

I installed the latest

That's clossing the backlass windows correctly, but still have a pinballx.exe running when exit
Nothing to see in the log file 

Posted
13 minutes ago, Tom Speirs said:

hmm. Ill look into it some more. Cheers.

Thanks. I will get a workaround in place: exit script "wait on exit" to no and put a wait in it.

Posted
13 hours ago, Tom Speirs said:

Should be resolved now. Thanks.

Nice one Tom!
You did it.
No pinballx.exe during closure anymore !
Good job
 

Guest
This topic is now closed to further replies.
×
×
  • Create New...