Proclaim Freezes

We have seen several instances while Proclaim is on air showing the lyrics for a song.

While going through the slides, the bottom area where it shows the slides with the pointer above the slide showing the current slide. Normally as you advance the slides, the pointer will reach the 2nd to the last slide currently up, you advance to the next slide it will shift the slides so the pointer is on the left side showing the current slide.

Sometimes (there does not seem to be anything that lets you know it will happen) when it is time to shift the slides to the left it will freeze for probably 5 to 15 seconds, then it will advance to the next slide.

It seems to happen more on slides with "motion" in them, but not sure if this conclusive. I have also been able to not make it happen if before advancing to the next slide I go ahead and shift the slides over.

Find more posts tagged with

Comments

Scott Alexander

Are you on Mac or Windows? If there is a presentation that reproduced this behavior in you group and you provide the name we can take a closer look. Also, if you can get it to happen reliably and post a log file from a session which reproduced the hang that will help as well.

James Horn

https://community.logos.com/discussion/comment/719369#Comment_719369

It is on Windows, group "DWMBC Presentation". Next time it happens I will capture the presentation, logfile, and which song it froze on.

Thank you for your help.

James Horn

https://community.logos.com/discussion/comment/719378#Comment_719378

We had a couple of hang ups this morning:

In Windows, group "DWMBC Presentation", during first service in schedule "May 3, 2015 Early", 3323.Proclaim May 3rd Early.log, during song "Since Jesus Came Into My Heart".

The second one, In Windows, group "DWMBC Presentation", during 2nd Service in schedule "May 3, 2015 Late", 6763.Proclaim May 3rd Late.log. during song "Great Is Thy Faithfulness"

James Horn

https://community.logos.com/discussion/comment/722827#Comment_722827

Scott Alexander (Logos) Wondering if you have had a chance to look at this or if you were able to get to the logs?

Scott Alexander

https://community.logos.com/discussion/comment/724340#Comment_724340

Hello James, thanks for submitting the logs. Unfortunately I'm not seeing anything that stands out. The situation you describe is when navigating forward in a presentation we attempt to auto scroll the timeline, keeping future slides in view. When new slides come into view we need to load them "into memory" so they can be displayed. Part of this loading process includes reading image data from the hard drive. If there is contention during this read you could experience a hang.

Since the hang is intermittent I wonder if another application on the computer is competing for hard drive access? Are you running anything else during the service? Any anti virus software running a scan perhaps?

James Horn

https://community.logos.com/discussion/comment/724346#Comment_724346

The Proclaim process is showing a consistent 25% CPU with over 450MB of memory being used. Is this a common thing for Proclaim or is this something I need to investigate further in the amount of space that our Proclaim "library" is using?

Also is there a way to verify there are no issues with the database that is synced up with what is stored in Proclaim? Maybe something to resync the information (like redownload what the "cloud" has)?

Spencer McKimson

https://community.logos.com/discussion/comment/724745#Comment_724745

Yes you can rename the database files in the data folder and they will reload upon signing in. Those are located at users/your username/appdata/local/proclaim/data/random string

James Horn

https://community.logos.com/discussion/comment/724747#Comment_724747

Before renaming the folders Proclaim was using a consistent 25% of the CPU and using 750MB+ of memory, plus when I closed Proclaim the Proclaim process continued to run at the same rate. I went ahead and killed the process, renamed the folders (there were two but one was probably old) and restarted Proclaim, after syncing the "library", we had no further "freezes" (which we did in an earlier service but not to the point of having to restart Proclaim), memory did not climb as high, cpu use looked more normal. Transitioning to the next slide and the "buffering" of the slides worked correctly.

Thank you for assistance in getting this issue fixed.