2014-06-19, 00:54
(2014-06-16, 16:51)joshua.lyon Wrote:(2014-05-31, 00:59)scarecrow420 Wrote:(2014-05-30, 20:50)pr0xZen Wrote: I run Win8.1pro on the 4GB stick mentioned at the bottom here (finally got them to list it) - never seen any hint at RAM shortage. Only "low memory warning" I ever got was a "false positive", a confirmed Windows bug.Interested in this statement. I have now a couple of times had windows 8.1 on my 2820 NUC displaying a "low memory" warning that takes focus away from XBMC, but task manager shows only 1GB of 4GB in use. Interesting you mentioned it's a confirmed bug, is there any resolution or more info you have seen?
(2014-05-31, 09:58)Crssi Wrote: In the last few week I get occasioanlly "low memory" pop up also on win 8.1 on NUC i5 haswell with 4Gb RAM.
Since I have changed nothing in the last year except I am up-to-date on XBMC nightlies, I would suspect that this is XBMC problem rather than Win 81, but this is only a speculation.
Does anyone knows more about this problem?
(2014-05-31, 12:52)pr0xZen Wrote: As mentioned it the post - not quite sure what triggers this "false positive", but as it doesn't affect all games and applications that would more likely eat up all available memory - there still has to be something specific that triggers it - and thus it must be a way to remedy it. I tried suggested solutions like bumping up swapfile size considerably, and making sure xbmc ran at the same resolution as windows itself, alternating "true fullscreen"/ fullscreen window - but saw no difference in the occurence of the errors. So I followed the instructions linked, and kept the swap file at ~2x RAM size. Have not seen a warning in 45 days and counting.I would caution against assuming that this is a false-positive. While I am not saying it was not a false positive in your case, I was experiencing a similar set of circumstances as you were and it turned out there was a memory issue. Occassionally I would come back to my XBMC PC displaying a low memory warning and when I would check memory utilization I would find the system in a normal state (eg. 1 GB usage in your example). After experiencing this several times, I figured something must be wrong so I put a System Monitor trace on memory and found that when I wasn't using the system the memory usage would slowly creep up and max out... when the low memory warning would come up it would force XBMC out of full screen (eg. bring the Windows warning to the front) and would allow the memory to drain back to a normal value. So when I would go to check the memory usage everything would be fine but it was actually the history I needed to track in order to see the low memory event.
My issue ended up having something to do with the resolution on my XBMC PC changing whenever I would turn off the receiver, which somehow wreaked havoc with XBMCs memory utilization. I have the HDMI from my HTPC routed through my receiver and then onto the TV. It turns out that whenever I would turn off my receiver the HTPC was switching to a much lower resolution. I tried several different fixes and I don't recall which (combination) of them resolved the issue, but here they are:
- XBMC: Use fullscreen window rather than true fullscreen: CHECKED
- WINDOWS: Manually set page file to 200MB - 1 GB
- HDMI: Tape pin 19 of HDMI cable
- GPU: Force output resolution to be fixed to 1920x1080
As others have said, using a fullscreen window rather than true full screen seems to avoid the out of memory error. But that gives me a different issue. When using fullscreen window, and the AVR/TV are switched off, the HTPC resolution changes and XBMC gets "bigger" on screen. Then when everything comes back on again, windows has reset to 1080P resolution but XBMC is stuck in a zoomed in mode, taking up the full screen but all zoomed in (only seeing perhaps 25-50% of the top left of the screen, maximised to fll the display). This is the only niggling issue I have! Obviously I just want my wife to be able to switch things on and have it ready to go but instead it's either XBMC all large and weird, meaning need to close/reopen it or hit the fullscreen button twice... or windows popped up an out of memory error which takes focus away from XBMC and needs to be dismissed and then alt tab back into XBMC. Neither are really wife friendly I tried the various fixes to the zoom issue, such as using a tool to create an INF driver from static EDID data to force the monitor drier to always be in 1080P etc, and running a remote VNC console to the HTPC to try and set the default resolution when the AVR/T are off (it doesn't seem to work - VNC console never indicates the res changes but yet sometimes when you turn things back on XBMC is all zoomed in and weird). I wish the memory leak issue could be fixed then I would just run in true fullscreen which also eliminates problems with the windows taskbar taking focus from XBMC sometimes etc. I guess my hope is for Intel to release new graphics drivers, if that is the cause of the memory leak