Version 8.1 > Memory Leak
2/23/2015 9:51:09 AM
We recently upgraded to a GFM Encore Prokey system running SSP 8.1. SSP is set up with two monitors, the second of which is being used for digital signage. When SSP is left unattended to run the signage, the system runs out of memory. Is this a known issue? Also, should SSP regularly consume 40-50% of the processor while running?
2/23/2015 2:11:48 PM
It is possible but none are known at this time.
Please contact the support team so that they can take a look at what you have and capture the content you are using. Once they have that they can pass it on for investigation. In most cases, both the memory leak and the CPU utilization will depend on the content. Are you running large, hi res videos in your digital signage?
Please contact the support team so that they can take a look at what you have and capture the content you are using. Once they have that they can pass it on for investigation. In most cases, both the memory leak and the CPU utilization will depend on the content. Are you running large, hi res videos in your digital signage?
2/24/2015 9:48:54 AM
No, the only videos running in the digital signage are 3 background HD motions I got from ShiftWorship.com. Everything is running in 16:9 format if that makes a difference.
2/24/2015 10:06:36 AM
I would not expect the format to matter but again we are not aware of any significant leak so we will need your content to test this out.
When you contact the support team another useful bit of info will be how long it runs before running out of memory. This is important so that we can make sure it is run long enough in testing.
If you are interested in trying to narrow down the culprit of the memory leak on your own you could do the following:
Determine the time it takes to run out of memory by running the slideshow.
Split your slideshow in half and run each half for that amount of time. If one half fails, split that in half and repeat.
Once you have it narrowed down, (hopefully to a single slide) you can send us that slide or reduced content.
If not just get with the support team to deliver the content you are having trouble with.
When you contact the support team another useful bit of info will be how long it runs before running out of memory. This is important so that we can make sure it is run long enough in testing.
If you are interested in trying to narrow down the culprit of the memory leak on your own you could do the following:
Determine the time it takes to run out of memory by running the slideshow.
Split your slideshow in half and run each half for that amount of time. If one half fails, split that in half and repeat.
Once you have it narrowed down, (hopefully to a single slide) you can send us that slide or reduced content.
If not just get with the support team to deliver the content you are having trouble with.
To post messages to the forums you must be signed in to a user account.