How would I do it? Well, first of all with Linux you do have the source code.
That is probably a good reason why it'sgood because people can fix bugs.
Then there is what software you choose to run. It you allow anything written
by anybody, sure you will have problems, but even then there is a difference
between applications and protected code. And modern processors have
protection built into them.
II don't own a Tesla and no virtually nothing about it, but I have written
large embedded systems that run 24/7 and control lots of dangerous powerful
industrial hydraulics and motors. I did NOT let people just install
whatever software they wanted and tried my best to vet whatever I did run.
I didn't trust things I didn't understand. I tried to keep things as
simpleas possible so I did understand it. I separated the user interface
from the real time stuff.
So you say the GUI is hogging memory. Can you run something simple like
"top"? Which processes are getting bigger?Do you know what they are? Can
you see what their parents are? Can you narrow it down from "leaks" to
"process with PID 2345"? Obviously that's the way to start debugging the
problem.
.On Thursday, April 18, 2024, 7:12:23 AM PDT, (-Phil-) <p...@ingineerix.com>
wrote:
I always try to produce good solid code, but it's not defeatist, it's reality.
Basically every modern OS and its stack of applications and drivers have
millions of lines and tens of thousands of developers, including a lot of
legacy code. Linux and MacOS are pretty good compared to Windoze, but the
fact remains, the leaks are there. I have real-time data from about 3000
Teslas (albeit most of them older), and the GUI shows marked increases in
resource usage and slowdowns after a month or so. Usually not a problem for
most Tesla owners because as Kevin points out, when a software update comes
down, there is a required reboot (usually at night while you are sleeping).
However, a lot of owners of salvage cars connected to my system eschew updates
and prefer to stick with the same solid release once they find one, so the
"free reboot" doesn't happen.
It's no different on a desktop or smartphone either. The more recent devices
have so much RAM and CPU that most people aren't going to notice a large
wastage. I reboot my phone at least once a month.
How do YOU propose YOU find and eradicate memory leaks without source code and
root access on your device? Even if you had all that, are you going to spend
thousands of man-hours debugging, compiling, optimizing and testing to fix it?
The mantra of today's software: SHIP IT.
On Thu, Apr 18, 2024 at 5:30 AM Lawrence Winiarski
<lawrence_winiar...@yahoo.com> wrote:
That's such a defeatist attitude. Memory leaks aren't inevitable and there
are lots of tools to find them. It's the result of shoddy, lazy programming,
not some fact of nature. Howevercomplicated you think the Tesla software
is, the Linux OS is much bigger project and more complicated and luckily Linus
has always had a low tolerance for stupid excuses.
On Wednesday, April 17, 2024 at 04:17:39 PM PDT, (-Phil-) via EV
<ev@lists.evdl.org> wrote:
Yes, you don't HAVE to reboot it. Same thing for your PC or phone, but all
modern software on complex systems with a large OS will have some amount of
memory leaks, so it's always a good idea to do an occasional reboot to
clear things up. I've seen Tesla uptimes without reboots of over 2 years,
but they are usually running like molasses by then.
Comparing the level of compute in a Zoe to the amount in a recent Tesla is
like comparing the Apollo Guidance computer to a modern PC. The
infotainment (main screen) in a Tesla is, in fact essentially a PC running
Linux. The autopilot computer adds a level of compute several orders of
magnitude over that.
On Wed, Apr 17, 2024 at 4:10 PM Rush via EV <ev@lists.evdl.org> wrote:
> Now, now, EV list lackey, calm down... just because it is recommended, it
> doesn't mean that the sky will fall on your head if you don't do it.
>
> My first M3 was bought in 2019 (I just traded it in for the refresh model
> because the FSD would transfer, a good deal if you ask me) and in those
> almost 5
> years I've done a reboot maybe 3 times....
>
> And I take issue with your blanket statement 'I can't imagine that the Zoe
> is
> any less computerized than a Tesla'. That, to me, just sounds like someone
> that's saying anything to put down Tesla's.
>
> Best regards,
>
> Rush Dougherty
> www.TucsonEV.com
>
>
>
>
> > -----Original Message-----
> > From: EV <ev-boun...@lists.evdl.org> On Behalf Of EV List Lackey via EV
> > Sent: Wednesday, April 17, 2024 3:41 PM
> > To: Electric Vehicle Discussion List <ev@lists.evdl.org>
> > Cc: EV List Lackey <evp...@drmm.net>
> > Subject: Re: [EVDL] Adding a FM radio to a Tesla
> >
> > On 17 Apr 2024 at 10:27, (-Phil-) via EV wrote:
> >
> > > It's normal to need to do the first simple 5 second reboot on Teslas
> > > every few weeks. Doesn't hurt anything and can make a sluggish UI
> > > fast again.
> >
> > That's considered NORMAL? Seriously?
> >
> > Insanity. You can't expect drivers to reboot their cars "ever;y few
> weeks."
> > I can just imagine how my low-tech other half, Margaret, would react if
> she
> had
> > to do that.
> >
> > But she's never had any such problem. We've owned our Renault Zoe EV
> for over
> > 4 years and have never had to reboot anything. It just works. And so
> does
> its
> > radio.
> >
> > I can't imagine that the Zoe is any less computerized than a Tesla. I
> suspect
> that
> > the Zoe's firmware is just more thoroughly debugged. Renault has a long
> history -
> > they're 136 years old - and a hard-earned reputation to protect.
> >
> > David Roden, EVDL moderator & general lackey
> >
> > To reach me, don't reply to this message; I won't get it. Use my offlist
> address
> > here : http://evdl.org/help/index.html#supt
> >
> > = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> >
> > It's the desire to be barbaric that makes governments call their
> > enemies barbarians.
> >
> > -- Bertolt Brecht
> >
> > = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> >
> > _______________________________________________
> > Address messages to ev@lists.evdl.org
> > No other addresses in TO and CC fields
> > HELP: http://www.evdl.org/help/
> >
> >
> >
> > --
> > This email has been checked for viruses by AVG antivirus software.
> > www.avg.com
>
>
>
> _______________________________________________
> Address messages to ev@lists.evdl.org
> No other addresses in TO and CC fields
> HELP: http://www.evdl.org/help/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.evdl.org/private.cgi/ev-evdl.org/attachments/20240417/d55f6129/attachment.htm>
_______________________________________________
Address messages to ev@lists.evdl.org
No other addresses in TO and CC fields
HELP: http://www.evdl.org/help/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.evdl.org/private.cgi/ev-evdl.org/attachments/20240418/14e7660f/attachment.htm>
_______________________________________________
Address messages to ev@lists.evdl.org
No other addresses in TO and CC fields
HELP: http://www.evdl.org/help/
