1.8rc3 Windows Player. "Low on memory" message after few hours of normal playing

Dear Developers,

Today, I got black screen. Before that the layout had been playing for 3-4 hours without noticeable problems.

I pressed i-button and saw string of errors similar to this (see the picture below): “C:\Program Files (x86)\Xibo Player\horiz\lib\48.mp4. Ex = Your computer is running low on memory. Quit other programs, and then try again.”

The layout consists of 4 videos - all in .h264.
PC spec: pentium lga 1155, 4Gb of RAM, windows 10 x64, video adapter - Intel HD graphics.
Two displays (TVs) are connected to HDMI and VGA output of video adapter.
The PC runs two instances of Xibo - horiz and vert - each for its own video output.
What could be the cause of this error?

Thank you.

It’s possible that two xibo players displaying videos simultaneously could be a bit too much for this PC.

If you restart it, could you take a look at ‘Performance’ tab in Windows task manager and see if the memory usage is increasing over the time?

Ok. I will track memory usage. Will report soon.

After 6-hours entered the same error state. No memory leaks were detected. All memory usage was ok (in resource monitor and task manager).
I have change dedicated video memory of Intel HD graphics in BIOS from 64 mb to 448 mb.
And now I will start watching GPU-memory instead of PC-RAM (by means of GPU-Z).
Probably hardware problem-but I will report later.

P.S.:If it is relevant. Half of all my videos are coded in /h264 and half are in vp8 codec. For vp8 I use LAV decoder. All codec from the latest k-lite codec pack.

Try to code the videos in Handbrake - www.handbrake.fr

Will take a look at handbrake. Thank you.

About “low on memory error”: Still squeezing down possible causes of this error:

So far I have:
1)If you search in Google “windows media player low on memory”, you will see that it is a very-very common error of media player. All suggestions are down to either reinstall windows media player or re-register all windows media player dlls (“for %a in (%systemroot%\system32\wm*.dll) do regsvr32 /s %a”)
2)probably problems with hardware decoding by means of LAV DXVA2 in k-lite codec pack.

Right now I reinstall windows media player and k-lite codec pack.

Will report soon after more testing

Nothing helped.
What I have tried so far.

  1. Reregistered and reinstall WMP
  2. K-lite code pack: use software decoding for h.264
  3. K-lite codec pack: use LAV hardware decoding for h.264
  4. Set paging file size to 4000 mb.
  5. Set dedicated video ram in bios from 64 mb to 448 mb.

Anyway after 3-4 hours of playing - I see errors for all of my .mp4 files - “You computer is running low on memory …”

Currently the fix is to convert all videos to vp8 codec. So far it seems a solution.

When I have time I will try:

  1. look for another h.264 codec
  2. try different Intel HD graphics driver.

I don’t think it is a bug of Xibo Player. Highly likely it is a bug of windows media player or graphic card driver.
I haven’t noticed any strange activities or problems with memory in Task manager, resource monitor, performance monitor (paging file counter).

Thank you.

Yeah, there are more topic regarding this error and WMP than I thought.

I think you did most things I can think about, I thought that if not the videos then the virtual memory, but you’ve tried that as well, I’m not sure what to suggest.

It would make more sense if the actual memory usage was really high after few hours, but as you say that’s not quite the case.

Unfortunately I do not have a sane way to recreate this issue locally, but if vp8 works for you, then I guess that’s the way to go at least on this device.

It’s been a year since this topic. I gathered more info on that.

  1. New hardware Core i7 8600, GTX1050ti latest driver, windows10 latest updates, latest k-lite, XIBO 1.8.7. Layout is made of video1.mp4, video2.mp4, video3.mp4. The same problem with h.264 and also the same with HEVC h.265 - video disappears after few layout loop cycles. Sometimes watchdog resets player, but I also had a situation with frozen picture on one display and frozen black screen on another display for good. The situation seems chaotic.
  2. Changing coding of video to Webm VP9 codec makes no problems so far.
  3. I haven’t tried different codec packs - I might need to - even if they use the same LAV decoder.
1 Like