[TIVIAR-ALPHA+] box freezes at end of IPTV timer recording

[reverend]

Hello all. Thisw doesnt happen every time. At the end of a timer recording of an IPTV stream, when the box is in standby, there is a freeze which i can only get past with a hard reboot. This is in the logs at the time of the freeze. Any help appreciated.

/dev/sda:
issuing standby command
06:57:44.0048 [NetworkTime] setting E2 time: 1673074664.00468
06:57:44.0067 [eDVBLocalTimerHandler] setUseDVBTime: current=dvb, new=dvb
06:57:50.6533 [Task] job Components.Task.Job name=SoftcamCheck #tasks=1 completed with [] in None
07:00:00.0093 [RecordTimer] activating state 3 (Ended)
07:00:00.0104 [RecordTimer] stop recording on tuner: (fallback) stream
07:00:00.0106 [eMP3ServiceRecord] stop recording

(enigma2:601): GStreamer-CRITICAL **: 07:00:00.040:
Trying to dispose element fsink, but it is in PLAYING instead of the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.


(enigma2:601): GStreamer-CRITICAL **: 07:00:00.061:
Trying to dispose element queue10, but it is in PLAYING instead of the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.


(enigma2:601): GStreamer-CRITICAL **: 07:00:00.061:
Trying to dispose element srcbin-src_0, but it is in PLAYING (locked) instead of the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.


(enigma2:601): GStreamer-CRITICAL **: 07:00:00.062:
Trying to dispose element hlsdemux10, but it is in PLAYING instead of the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.

07:00:02.6256 [gRC] main thread is non-idle! display spinner!