So today I hopped into my Tesla and started fiddling with the nav display. It couldn't keep up very well with my screen presses, and would momentarily go into a screen locked state - during these times, the AC and fan turned off. This happened about four times where the AC/fan would turn off for a few seconds at a time. In a hot car on a hot day, this was very annoying. Not only was the nav system fritzing out, but the climate control system was being affected by it. I attribute this to the Tesla running Linux as the OS for the car displays and controls. I can only guess that it has a regular virtual memory system (since the symptoms seemed consistent with pages being swapped in and out of memory). While such an OS is fine for a desktop or server general purpose PC, it most certainly is not a good choice for a car control system. A car must be able to walk and chew gum at the same time - in particular, if there are critical things the OS must do to keep the climate control system happy (like checking the temperature sensors and giving fan speed instructions), those processes must be at a very high priority, and in particular, cannot be interrupted by page swaps. Indeed, there shouldn't even BE page swaps. The car computer should have an adequate amount of ECC memory to never need a VM system. You aren't running Microsoft Word on it, afterall. A RTOS (like QNX) would be able to deal with fast interrupts from users and the car sensors without dropping important functions. Whenever I see software bugs in the car, they usually appear to be symptoms of using Linux instead of a robust RTOS. I am worried that Tesla will never be able to fully get the car computer/control system working without bugs unless the underlying architecture gets a rework. People asking for all sort of fancy features may be waiting a long time if they can't get basic functionality to work (like have a climate control system that doesn't get affected by user input presses in a completely unrelated function).