Thank you
That is in line with what has been seen from others - with Plex Commercial Skipper.exe getting an Access Violation 0xc0000005 exception / crash.
We do not know the cause at this moment but has been raised as an issue with our development team.
Thanks for letting us know that its at least a known issue with the dev team. I was curious if anyone had the issue fixed last week, since the commercial skipp was mentioned in the notes.
Does staff need any more logs? is there anything we can be trying to get the Commercial Skipper working?
Following…
I continue to have the same issue.
Plex Media Server is installed on Win 10 Pro
In case it helps Development get this issue resolved faster, I’m providing some information about my configuration. If we notice everyone with the crash has some similarity then that item may be related to the crash. Conversely, we can eliminate certain items if there is great diversity for that item.
My config probably seen less often:
Intel Xeon E3-1245 v5 CPU with C236 chipset
32 GB ECC memory (unbuffered)
Less likely cause config:
Nvidia Geforce GTX 1050 Ti GPU (driver 446.14)
Intel HD Graphics P530 GPU (built-in to CPU)
Not using “Use hardware acceleration when available” (unchecked)
Not using “Use hardware-accelerated video encoding” (unchecked)
Two PCIe NVMe SSD drives
Three SATA WD Red HDs (JBOD)
PMS started with “-noninteractive” option (Windows service with normal user account)
Even less likely cause config:
Windows 10 Home version 2004 (also had problem with version 1909)
PMS version 1.19.4.2935 (works fine with PMS 1.18.5.2309, crashes with all versions after)
TV Tuner: HDHomeRun Connect Quatro (HDHR5-4US) (firmware 20200521)
Please let us know what other information Development needs to make progress on this bug, or if you need justification to raise bug priority for this issue.
It looks like it’s now cutting commercial segments from the recordings again with the latest update. That said, my post-processing script seems to be broken now.
EDIT: Nope. Still broken.
Does anyone know if the path to the script has to be fully qualified, a la, “C:\Users\wct\AppData\Local\Plex Media Server\Scripts\PlexPostprocessingScript.bat” or can I just use PlexPostprocessingScript.bat as long as it’s in the new Scripts sub-folder?
This doesn’t answer your question but I have found that it fails to run if it is entered with “QUOTES” not sure why…
HTH.
EDIT: in response to WCTschumy post processing q?
I guess that means plex will properly parse the spaces in the “Plex Media Server” part of the path?
Just a wild guess, but because the path would nearly always have spaces (for Plex Media Server), they may be programmatically adding quotes to the path before passing to the OS/API. If so, if you include quotes, then it will try to find an actual path with quote marks in it and fail. Also, if this is what they are doing, it would have been better to examine the path first and see if it includes opening and closing quotes and only add quotes when they were not already there.
Since they’re requiring the scripts go into the scripts folder from now on, I wonder if the path is needed at all. At this point, I’m tired of mucking with it…
Maybe sa2000 would kindly give us an update.
Can confirm that the issue still persists in Version 1.19.5.3006.
I’m confirming that “Plex Commercial Skipper.exe” still crashes with PMS version 1.19.5.3021
@sa2000 Could you please give us an update on the status of this bug? Are the developers still unable to determine the cause? If so, what information do they need to help resolve this issue? Instead of working with just one person, would it help to get log/trace/debug info from several of the many people experiencing this issue? If you check earlier in the thread, I provide some system configuration information in addition to Windows event viewer crash entries. I suspect the majority of people affected by this bug would be happy to provide information if it helped resolved the issue. Let us know how we can help get this resolved.
This is the commmand line from a dump for one of the Access Violation crashes of the program - you can see thel paths that have space characters are with a double quote
"C:\Users\SA\Documents\Builds\plex-media-server\build\binaries\Debug\Plex Commercial Skipper.exe" --ini=C:\Users\SA\Documents\Builds\plex-media-server\build\binaries\Debug\Resources\comskip.ini --output=C:\Users\Public\Plex-Tests\Videos3\.grab\4664ec375bd719db5db810a112bafb9126063601-b79fcbfb64fa3ca58f3ef8e115327951a2cb9f4c -t --verbose=1 "C:\Users\Public\Plex-Tests\Videos3\.grab\4664ec375bd719db5db810a112bafb9126063601-b79fcbfb64fa3ca58f3ef8e115327951a2cb9f4c\Infomercial - S2019E51 - Brand Developers Sunshine Blade Instant Heat.ts"
The plan was to update comskip version as our version is a few years old.
was? Is there a timeline for this? Is this still the plan of record?
Thanks! WIll.
It is still but will also try and understand why it is crashing
I don’t have a timeline but I have given it a bump
Bump. Tired of testing new builds then have to uninstall and reinstall the older build that works.
I’m really disappointed, too! I don’t have the inclination or time to reinstall the older versions, and I’m just getting frustrated. I really like Channels when I did their trial. If there’s no fix From Plex soon…
