This is probably the case.
OK, I've managed to find the info now. The full 1G is split between GPU and CPU and the split is configured in /flash/config.txt using the gpu_mem setting.
On the OpenELEC forums it states that 320M is the default, so that kind of fits what I'm seeing.
I'm currently running LE on a Pi 3 and noticed that the total RAM reported by free -m was only showing 736M. This seems low for a board specced with 1G of RAM. Is the RAM used elsewhere i.e. video memory etc ?
This is what free -m reports on a Pi 3:-
total used free shared buffers cached
Mem: 736 319 417 5 38 139
-/+ buffers/cache: 140 595
Swap: 0 0 0
Does for anyone timeshift works in version Tvheadend 4.2 from libreelec repo?
I know it was working in older version that have Milhouse compiled in OpenELEC but in latest builds it does not.
This is the smoothest I've had timeshift work so far.
I have however uncovered a potential bug. I've set timeshift to use disk only, but timeshifting eventually consumes available RAM on my Wetek Play. I've even tried setting the "Maximum RAM size (MB)" to 1, just in case having it set as 0 was being interpretted as unlimited.
I'm currently running 4.1-2047 from the builds at index - powered by h5ai v0.29.0 (https://larsjung.de/h5ai/), but have also seen this in the older 4.0.9 from the repo
When available RAM eventually drops to around 80M, the dmesg log gets filled with:-
[ 745.936394@0] balance_pgdat end zone=1, pgdat_is_balanced=0
[ 745.936528@0] balance_pgdat, nr_reclaimed=8
[ 745.936559@0] balance_pgdat end zone=1, pgdat_is_balanced=0
[ 745.936706@0] balance_pgdat, nr_reclaimed=30
Once playback of the channel is stopped, all the comsumed RAM is released back to the system again.
The only way to keep timeshifting enabled without consuming RAM is to enable "On-demand (no first rewind)" so it would only start buffering if/when I pause TV.
