openlp crashes on windows when displaying images

[John Cegalis]

Windows build 1970. This did not happen in 1964.

I have a group of images and I started looping them. After so long openlp crashes with a windows error. I attached a debug log and cut out the repeats all through the center. In this instance it appears to have taken almost 2 hours. This morning during the church service it only took an hour. Yesterday I had it on 1 image only with no looping (obviously) and it crashed with the windows error. I have never had openlp crash in any way in the last year.

[John Cegalis (jseagull1)]

This is Win7

[John Cegalis (jseagull1)]

Further testing I displayed a single image in rev 1967 and let it go. Looking at the time it crashed 9 hours later. The debug log was 64 meg and I cut out the middle which was all the same. It crashed 20 minutes before I got up and looked at it. I am now testing 1964.

[John Cegalis (jseagull1)]

I don't want to flood this bug but this is new. rev 1964. It starts out looping with memory usage around 355000. The last I looked before the traceback is was up to 1.2 gig. When I closed the traceback it immediately popped up again. I was running in debug but the log was reset. This all happened in a period of about an hour.

Traceback (most recent call last):
  File "D:\OpenLP_Code\rev-1964\build\pyi.win32\OpenLP\out01-PYZ.pyz\openlp.core.ui.slidecontroller", line 1292, in timerEvent
  File "D:\OpenLP_Code\rev-1964\build\pyi.win32\OpenLP\out01-PYZ.pyz\openlp.core.ui.slidecontroller", line 1176, in onSlideSelectedNext
  File "D:\OpenLP_Code\rev-1964\build\pyi.win32\OpenLP\out01-PYZ.pyz\openlp.core.ui.slidecontroller", line 1100, in slideSelected
  File "D:\OpenLP_Code\rev-1964\build\pyi.win32\OpenLP\out01-PYZ.pyz\openlp.core.ui.maindisplay", line 302, in image
  File "D:\OpenLP_Code\rev-1964\build\pyi.win32\OpenLP\out01-PYZ.pyz\openlp.core.ui.maindisplay", line 310, in displayImage
MemoryError

[Raoul Snyman (raoul-snyman)]

It looks like there is a memory leak in the remotes plugin. Switch it off and test again.

[John Cegalis (jseagull1)]

The church computer I use has 3 video cards in it. I use the third video card for stage viewing on Firefox, dragged over to the 3rd display for the rear projector.
I tested looping images on rev1970 without Firefox running or the stageview and it went for 3.5 hours without an issue. I opened Firefox again with stageview and it crashed after a couple hours. Memory usage was up to 1.5 gig when it crashed.
This is as much as I know.

[Andreas Preikschat (googol-deactivatedaccount)]

Set to Medium, as it does not affect everybody/does not occur under normal conditions. Also it does not seem to be regression.

[John Cegalis (jseagull1)]

On Raoul's request I re-tested this on Win7 2049. I had a group of images cycling every 20 seconds for 7 hours. Memory usage when I shut it down was 1.15 gig and it was working fine but the memory usage was still climbing in that time. The same with above, it started out looping with 355000. I suppose you have to decide if you want to find the memory leak or not.

[Raoul Snyman (raoul-snyman)]

This seems like a very corner-case bug which few are able to reproduce. I think we should move it to 2.1.

[Raoul Snyman (raoul-snyman)]

Downgrading this to a low as it is a very corner-case scenario. I've moved it to 2.1.

[Tim Bentley (trb143)]

Marking as wont fix - Please confirm if this is still a problem as 2 years have passed.