4 ms·
Given that Rust prevents invalid memory accesses and enables fearless concurrency, this is probably caused by some kind of memory leak or deadlock. In this cas
by blub 4y ago
Given that Rust prevents invalid memory accesses and enables fearless concurrency, this is probably caused by some kind of memory leak or deadlock.
In this case, the older blinks are possibly not deallocated and slow down the processing of newer blinks. Fortunately automotive software has all sorts of watchdogs and at some point the blink watchdog must kick in and it kills the blink manager which is then restarted and it processes the blink queue in quick succession.
- lenkite 4y agomemory safe - correct. But "fearless concurrency" is mostly plain propaganda. Lots of deadlockable code in Rust. You still need to pay close attention to structuring code for concurrency and some libs are deadlock prone in async.
- hcarvalhoalves 4y agoIt’s so f**ing stupid we’re discussing memory leak or concurrency issues of a TURN SIGNAL. I’m never buying a car from the 2020’s.
- deleted 4y ago[deleted]
- jeffrallen 4y agoPeople who say "fearless concurrency" have clearly never debugged a bad concurrency problem. Those strike fear into the heart of any honest hacker, and no amount of nagging from the compiler or good marketing can make concurrency fearless. I understand what the marketing means. But grep your codebase and dependencies for "unsafe"... That should put paid to your fearlessness.