Closed pbertra closed 4 years ago
No Problems with Mono 6.12.0.182
As far as I can remember, the problem was creating a new WebClient caused this problem. Now we are reusing the WebClient Class. Please try to update to the mentioned version. Otherwise we have to check if we have a different problem.
Updated the version of Mono to the latest 6.12.0.200, sadly the problem still persists.
A few seconds after the start of Teslalogger it eats up 100% of one core.
After the start of Teslalogger it is common to use a lot of CPU to update the database and do some housekeeping. But if after lets say 1 hour the problem still persists, we have a problem.
Please run Teslalogger for at least one day.
Get the PID of teslalogger:
Use the PID in following command:
top -H -p 487
Post a screenshot like this:
I let it run for about one day, but it stays at 100%.
Here´s the output you requested:
Looks like it's generating maps for the timeline.
Could you please post a logfile, so we can see if it's a endless loop or really generating maps for the timeline
Logfile Teil 1 logfile1.zip
Logfile Teil 2 logfile2.zip
Could you please post a logfile, so we can see if it's a endless loop or really generating maps for the timeline
Did you see my post?
I run the lastest version of Tesla Logger in docker (updated from the admin page) and every time, after a few hours, the teslalogger container starts using cpu constantly (20% of my cpu).
If I restart it, it drops to less than 5% until some unknown problem that causes it to use more CPU. The log doesn't give any information when this triggers.
Other containers don't use more than a few % CPU.
Car Version: | 2020.8.2 Last Update: | 27/03/2020 à 19:18:56 Teslalogger: | 1.39.0.0