Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

Diagnosis of "High Memory Consumption"

This site may earn commission on affiliate links.
I just got my (2017) S back from the Brea service center. I had two issues that led to the visit. In the first, the center display (but not driver one) would turn black at random intervals. It would remain black until I rebooted the display. The second is that streaming stations would skip and pause, a bit like old car CD players did in the nineties.

The service center looked at the car and informed me there were signs of "High Memory Consumption" that were the cause of the problem. When I picked up the car I was told it was due to (1) browser use, and (2) "a lot" of recent trips stored in memory. I told them that I don't use the browser at all, so they said it's because the car stores a lot of information for each trip and it needs to be periodically cleared. The service adviser first claimed it can only be done during a service appointment, but then a technician showed up and said I can clear individual trips from recent history by swiping each one to the right.

Has anyone heard of high memory usage issues? Why can't a Tesla handle routine usage for a year and a half, during which I searched destinations and drove to them? Can't the system free its own RAM, for example by deleting the oldest trips first? The technician's comments about browser use include "we recommend not visiting sites that use 'live data' and consume high amounts of memory for an extended period of time". Since I don't use the browser, this didn't really apply.

The solution was to delete all my recent trips, which seems to have cleared up both problems. Has anyone heard of this issue or run into it? Does the diagnosis sound correct?
 
  • Informative
Reactions: Brettski
I just got my (2017) S back from the Brea service center. I had two issues that led to the visit. In the first, the center display (but not driver one) would turn black at random intervals. It would remain black until I rebooted the display. The second is that streaming stations would skip and pause, a bit like old car CD players did in the nineties.

The service center looked at the car and informed me there were signs of "High Memory Consumption" that were the cause of the problem. When I picked up the car I was told it was due to (1) browser use, and (2) "a lot" of recent trips stored in memory. I told them that I don't use the browser at all, so they said it's because the car stores a lot of information for each trip and it needs to be periodically cleared. The service adviser first claimed it can only be done during a service appointment, but then a technician showed up and said I can clear individual trips from recent history by swiping each one to the right.

Has anyone heard of high memory usage issues? Why can't a Tesla handle routine usage for a year and a half, during which I searched destinations and drove to them? Can't the system free its own RAM, for example by deleting the oldest trips first? The technician's comments about browser use include "we recommend not visiting sites that use 'live data' and consume high amounts of memory for an extended period of time". Since I don't use the browser, this didn't really apply.

The solution was to delete all my recent trips, which seems to have cleared up both problems. Has anyone heard of this issue or run into it? Does the diagnosis sound correct?


I have a version 2 car. During a service visit for an unrelated item, the ranger told me that recent trips should be cleared in order to not overuse the memory.
 
I’ve tried this “trick” several times.
I have the skipping stuttering music and all of the aforementioned issues a lot since the latest software.
Honestly I’ve seen little to no difference I can tell by clearing the recent trips.
I think there is simply more to it than this.
Others have suggested a deeper problem in frame rate use and things like live traffic being updated way more than it needs.
Most can see this by simply using the sketch pad Easter egg and immediately the problem stops.
 
I have cleared 15 months of previous trips. While it helped the overall responsiveness of my MCU1 display, I still have skipping and stuttering for streaming content (TuneIn). This will (hopefully) get corrected with a software update as Tesla makes their code more efficient. I say that with a healthy bit of skepticism and don't believe that this should be an owner's responsibility to manage.
 
There are like 10 recent threads on this topic. Yes, it's a known issue with the first generation MCU. Yes, problems like this shouldn't exist.
It sounds more like a problem with the software Tesla wrote for the first generation MCU. Or, and this is more likely, a problem with the software Tesla wrote for second generation MCU and then jammed it onto the first generation MCU because they are obligated to support it, but don't care to spend the time to maintain it separately.
 
I’ve tried this “trick” several times.
I have the skipping stuttering music and all of the aforementioned issues a lot since the latest software.
Honestly I’ve seen little to no difference I can tell by clearing the recent trips.
I think there is simply more to it than this.
Others have suggested a deeper problem in frame rate use and things like live traffic being updated way more than it needs.
Most can see this by simply using the sketch pad Easter egg and immediately the problem stops.
Turn off traffic on the nav, that helps quiet a lot. There is whole other thread about this elsewhere on TMC, a friendly hacker pointed out that v9 checks for traffic 1000 times more often than it should (every 120ms instead of every 120s), causing massive CPU load, which leads to overheating, which leads to further slowdown. It has been reported to Tesla since v9 (all MCU browsers died), but nobody has confirmed a released fix (MCU1 fixes are way down the priority list for Elon).
 
There’s a report that the live traffic issue (at least) is fixed in 2019.16.x. A new version of that (16.2) started rolling this AM so perhaps we can check this out more widely soon.

This sort of thing (Max N recent trips) really should be an easy (trivial) software fix....