Vero 4k regular crashes in idle

Edit: it’s possibly one plugin I forgot I installed.

When I restart the Vero (because it crashed), I can watch one or many movies, avi or mp4. Then I switch off the screen and the AV receiver. Vero keeps running. After a while, when I come back to it, it shows the red light and is unresponsive.

I started the logging, rebooted, had the Vero play a movie, and stopped the movie. As always, I turned off the screen and the AV receiver.

This log is generated via grab-logs -A right after reboot.
https://paste.osmc.tv/kamufarira

I extracted this part here: http://paste.osmc.tv/etisehequf which points to a python exception thrown while probably updating the library. I turned regular library updating on in the configuration.

Edit: ah, it’s not in the configuration, it’s a plugin I forgot I installed (library auto updater). I disabled the cleaning of the database now.

Does the issue go away if you disable the library watchdog add-on?

it’s like 5 hours now with the automatic clean-up (not: automatic update) of the library turned off, and the vero hasn’t crashed. It seems to be related with the automatic library clean-up.

Well, this was too early. I watched a movie, and sometime later, the vero showed me the red light. So I rebooted, and disabled the plugin completely.

It crashed again. So I rebooted, turned on logging, rebooted, watched a movie (or rather: had my empty chair watch a movie), came back later and: red light.

The log is here:
https://paste.osmc.tv/eyogidajad

How can I use the vero without pulling the plug each time before a movie?

It still looks like a overheating which normally is tough to find. But we have seems Library updates possible sources. How do you have Library Updates configured now that you have watchdog disabled?

I haven’t configured any automatic Library Updates. I’d do it manually or try the plugin again once the crashing was sorted out.

Ok, then need to dig in to find the culprit.
I would suggest to open two SSH connections (best in the ssh session start a screen session).
In one window have tail -f .kodi/temp/kodi.log running
In the other one have watch cat /sys/class/thermal/thermal_zone0/temp

Indeed, for whatever reason, the temperature seems to be lower when watching a movie. Afterwards it increased from 92 to 117, then at ~14:30 the connection broke down, vero crashed.

tail -f kodi.log

osmc@osmc:~/.kodi/temp$ tail -f kodi.log 
2020-06-24 13:49:56.451 T:4068012032  NOTICE: Fallback resolution at 16 + 7 01080050.00000pstd
2020-06-24 13:49:56.451 T:4068012032  NOTICE: Found resolution 1920 x 1080 with 1920 x 1080i @ 60.000000 Hz
2020-06-24 13:49:56.451 T:4068012032  NOTICE: Fallback resolution at 16 + 8 01080060.00000istd
2020-06-24 13:49:56.451 T:4068012032  NOTICE: Found resolution 1920 x 1080 with 1920 x 1080i @ 59.940060 Hz
2020-06-24 13:49:56.451 T:4068012032  NOTICE: Found resolution 1920 x 1080 with 1920 x 1080 @ 60.000000 Hz
2020-06-24 13:49:56.451 T:4068012032  NOTICE: Current resolution setting found at 16 + 10
2020-06-24 13:49:56.451 T:4068012032  NOTICE: Found resolution 1920 x 1080 with 1920 x 1080 @ 59.940060 Hz
2020-06-24 13:49:56.451 T:4068012032  NOTICE: Found best resolution 0192001080060.00000pstd at 26, setting to RES_DESKTOP at 16
2020-06-24 13:49:56.714 T:4068012032   ERROR: GetString: error reading /sys/firmware/devicetree/base/buggymali
2020-06-24 13:49:56.890 T:4068012032  NOTICE: Updated resolutions and set desktop
Connection to vero closed by remote host.
Connection to vero closed.

Which skin are you using.
Actually just to get the right picture the Vero didn’t crash at 120c it shuts down gracefully to avoid damage

Maybe enable debug logging to see more details

That’s also what I wonder.
Trying the OSMC skin to rule out a problem with a skin would be a good idea.

In fact, I am using the default OSMC skin. (Is that the corresponding message in the log? 2020-06-24 10:57:24.540 T:4068012032 NOTICE: load skin from: /usr/share/kodi/addons/skin.osmc (version: 18.3.0?)I have been using that for a long time now. The requested debug log is attached in Vero 4k regular crashes in idle. Please let me know if you want another debug log.

I meant enabling debug logging now and have the temperature check running and the tail to narrow down what keeps Kodi busy while temperatures increase

Ah, understand. Enabled debug logging, restarted, ran a movie. Movie ended, temperature rose to 117, kodi switched off. Unfortunately, the ssh session ends then, and since I grabbed the output in screen, I cannot scroll up to get the remainder of the log. But anyway, the movie ended at 20:18.

2020-06-24 20:18:21.218 T:4068679680   DEBUG: DeleteRenderer - deleting renderer
2020-06-24 20:18:21.219 T:4017091296   DEBUG: CActiveAESink::OpenSink - ALSA Initialized:
2020-06-24 20:18:21.219 T:4068679680   DEBUG: CAMLVideoBufferPool::~CAMLVideoBufferPool: Deleting 6 buffers
2020-06-24 20:18:21.219 T:4017091296   DEBUG:   Output Device : Default (AML-M8AUDIO: HDMI, S/PDIF & analogue)
2020-06-24 20:18:21.220 T:4068679680  NOTICE: VideoPlayer: waiting for threads to exit
2020-06-24 20:18:21.220 T:4068679680  NOTICE: VideoPlayer: finished waiting
2020-06-24 20:18:21.220 T:4068679680  NOTICE: CVideoPlayer::CloseFile()
2020-06-24 20:18:21.220 T:4068679680  NOTICE: VideoPlayer: waiting for threads to exit
2020-06-24 20:18:21.220 T:4068679680  NOTICE: VideoPlayer: finished waiting
2020-06-24 20:18:21.221 T:4017091296   DEBUG:   Sample Rate   : 44100
2020-06-24 20:18:21.221 T:4017091296   DEBUG:   Sample Format : AE_FMT_S32NE
2020-06-24 20:18:21.222 T:4017091296   DEBUG:   Channel Count : 8
2020-06-24 20:18:21.222 T:4017091296   DEBUG:   Channel Layout: FL, FR, LFE, FC, BL, BR, UNKNOWN1, UNKNOWN1
2020-06-24 20:18:21.223 T:4068679680   DEBUG: Radio UECP (RDS) Processor - delete ~CDVDRadioRDSData
2020-06-24 20:18:21.223 T:4017091296   DEBUG:   Frames        : 2048
2020-06-24 20:18:21.224 T:4068679680   DEBUG: CGUIWindowManager::PreviousWindow: Deactivate
2020-06-24 20:18:21.225 T:4017091296   DEBUG:   Frame Size    : 32
2020-06-24 20:18:21.226 T:4068679680   DEBUG: ------ Window Deinit (VideoFullScreen.xml) ------
2020-06-24 20:18:21.235 T:4027577056   DEBUG: CActiveAE::ClearDiscardedBuffers - buffer pool deleted
2020-06-24 20:18:21.239 T:4068679680   DEBUG: Previous line repeats 1 times.
2020-06-24 20:18:21.239 T:4068679680   DEBUG: CGUIWindowManager::PreviousWindow: Activate new
2020-06-24 20:18:21.246 T:4068679680   DEBUG: ------ Window Init (MyVideoNav.xml) ------
2020-06-24 20:18:21.247 T:4068679680   DEBUG: [Warning] CGUITextureManager::GetTexturePath: could not find texture 'noop'
2020-06-24 20:18:21.249 T:4068679680   DEBUG: CGUIMediaWindow::GetDirectory (videodb://tvshows/titles/25/2/?tvshowid=25)
2020-06-24 20:18:21.249 T:4068679680   DEBUG:   ParentPath = [videodb://tvshows/titles/25/2/?tvshowid=25]
2020-06-24 20:18:21.275 T:4068679680   DEBUG: WindowVideoNav::GetDirectory
2020-06-24 20:18:21.293 T:3644855008   DEBUG: Thread BackgroundLoader start, auto delete: false
2020-06-24 20:18:21.371 T:3644855008   DEBUG: Thread BackgroundLoader 3644855008 terminating
2020-06-24 20:18:21.377 T:3624891104   DEBUG: ffmpeg[D80F72E0]: [swscaler] No accelerated colorspace conversion found from yuv420p to bgra.
2020-06-24 20:18:21.501 T:4068679680   DEBUG: ffmpeg[F2832000]: [swscaler] No accelerated colorspace conversion found from yuv420p to bgra.
2020-06-24 20:18:21.503 T:4068679680   DEBUG: [Warning] CGUITextureManager::GetTexturePath: could not find texture 'noop'
2020-06-24 20:18:21.669 T:3076854496   DEBUG: DoWork - took 339 ms to load special://skin/extras/backgrounds/1.jpg
2020-06-24 20:18:51.385 T:3624891104   DEBUG: Thread JobWorker 3624891104 terminating (autodelete)
2020-06-24 20:18:51.408 T:4068679680   DEBUG: SECTION:UnloadDelayed(DLL: libamcodec.so)
2020-06-24 20:18:51.671 T:3076854496   DEBUG: Thread JobWorker 3076854496 terminating (autodelete)
2020-06-24 20:21:21.284 T:4068679680   DEBUG: CAddonSettings[screensaver.xbmc.builtin.dim]: loading setting definitions
2020-06-24 20:21:21.284 T:4068679680   DEBUG: CAddonSettings[screensaver.xbmc.builtin.dim]: trying to load setting definitions from old format...
2020-06-24 20:21:21.285 T:4068679680   DEBUG: ------ Window Init () ------
Shared connection to vero closed.

Yeah that is the issue with screen. Actually if it is so easy to reproduce would not need screen just do a ssh session.
Anyhow we as we now know that it increased right after the movie and have the time stamp we can check the kod.log.old. Just upload that via grab-logs -X

But I am really suprized what could raise the temperature within 20 seconds so much.

Voilà: https://paste.osmc.tv/rejubuwiye
But let me add that it was 20:18 when the movie stopped and 20:54 when kodi gracefully shut down to prevent heat damage at 117°C. It’s just not seen in the logfile, because no further message was printed by kodi. So it is approximately 35 minutes between movie end and heat shut down.

osmc@osmc:~$ cat temperature.sh 
#!/bin/bash
while true
do
	echo "$(date '+TIME:%H:%M:%S'): $(cat /sys/class/thermal/thermal_zone0/temp)" | tee -a ~/logfile.txt
	sleep 10
done
osmc@osmc:~$ cat logfile.txt 
TIME:19:33:52: 60000
...
TIME:19:39:55: 64000
...
TIME:19:55:07: 70000
...
TIME:20:06:19: 73000
...
TIME:20:18:11: 74000
TIME:20:18:21: 76000
TIME:20:18:31: 82000
...
TIME:20:19:11: 87000
...
TIME:20:21:01: 92000
...
TIME:20:23:31: 97000
...
TIME:20:27:52: 102000
...
TIME:20:33:12: 107000
...
TIME:20:41:53: 112000

...
TIME:20:54:45: 117000
osmc@osmc:~$

That’s really strange.
After playing then movie was the Veron on a Menu where here was a srcolling text?
It would be really strange if Kodi eats all the CPU without anything in debug logging.
Suggest to open a 3 rd SSH session to check with htop if Kodi is really the main CPU user when the device overheats.

Did that. Vero gets back to the episode screen with scrolling text. In this phase, top reports that kodi eats up to 75% CPU. To compare, it’s 46% while playing the movie, and 44% in kodi’s start screen.

Is there anything I can do about that? Can the scrolling text be disabled, or can I use a screensaver which inhibits the scrolling text from eating up CPU? Or can kodi jump back to the season or series overview?

Or… can the scroll feature be programmed in a way that it does not eat up plus 30% (45 => 75) CPU?

Edit: just switched back to the season screen. 26% CPU.

This is all still strange. If I stand on a season with scrollng text I have Kodi at 72% - 85% CPU. But the temp is stable around 82c.

So what could be a suitable next step to track this down?

Clearly a tough one.
My recommendation would be to make a backup and try a clean reinstall first to determine if that without any addons is stable