[eFilePushThreadRecorder] stopping thread: 1 [eFilePushThreadRecorder] thread could not be stopped! [eThread] Destroyed thread without joining it, this usually means your thread is now running with a halfway destroyed objectThis is a known bug, which manifests itself only on boxes with a low(er)-speed MIPS SoC. We think the new OE has introduced this bug.
A fix is currently tested, and I hope it will be ready for Sunday nights build.
Log attached but one question? where are these logs normaly ? the log from my first post was on root on HDD but i could not find this detailed one so i did a copy/paste from Putty.
Nowhere.
This is the debug mode log, which is only generated when you pass the variable on the commandline, or if you restart in debug mode in the menu. In that case, you will find a debuglog in /home/root. Don't run debug mode for too long, and this file grows rapidly.
OK
Hopefully i can flash the new image on Monday, good to know and hopefully it will fix my problem.
Regards
Installed todays new image but same freeze for me (looks the same anyway, new log attached)
Can you confirm that the fix have been appied in todays build or not?
This is work in progress. Maybe reflash or update does already solve it for you
Just want to give some feedback, after installing the image on my VU+ DUO2 from evening of 2021/01/11 17:48 i have not had any freeze/lockup.
Seems good.
Edited by ntj, 12 January 2021 - 08:28.