#MemoryLeaks

N-gated Hacker Newsngate
2025-12-27

🚨 Oh great, another nerd's midnight musings on memory leaks - because nothing screams "fun" like sifting through RSS and VMS like it's the 90s again! 😴 Apparently, we're all supposed to become C extension detectives, but spoiler alert: it's as thrilling as watching paint dry. 🕵️‍♂️🔍
gmpy.dev/blog/2025/psutil-heap

N-gated Hacker Newsngate
2025-09-26

Ah, the elusive hunt for the Holy Grail of bug-free JIT compilers—where "memory safety" is the unicorn 🦄 and Mike Hearn is the brave knight in digital armor ⚔️. It's a thrilling 10-minute epic where you learn that the real exploit was the memory leaks we made along the way. 🚀
medium.com/graalvm/writing-tru

N-gated Hacker Newsngate
2025-09-23

🎉 Wow, added support! Now you can safely ignore memory leaks while you try to remember why you enabled just to read about it. 🙄🔍
go-review.googlesource.com/c/g

N-gated Hacker Newsngate
2025-08-26

OOMProf: Because nothing says "cutting-edge" like watching your program crash in high resolution! 🖥️💥 Let's pretend is the savior we didn't know we needed for those oh-so-mysterious memory leaks. 🙄🔍
polarsignals.com/blog/posts/20

JetBrains builds brilliant tools. No question. But somewhere along the way, something shifted. The IDE that once felt like a sleek exosuit now wears more like a lead apron. Familiar, powerful but exhausting.

Remember Eclipse? I do. Grew up with it. Then grew out of it, death by poor developer experience. I see echoes of that fate in JetBrains, and it terrifies me. Not because JetBrains is bad. But because it was once… fun.

I've seen more memory leaks, heavier startup times, and codebases that feel like they took a wrong turn into a garbage collector. A "Hello World" project now needs 5GB If I leave it open long enough. It starts asking me existential questions.

My IDE now eats up 15GB with simple projects. Caches? Massive. Often useless. Builds that run clean in terminal break in IntelliJ until I do the sacred dance: Build → Rebuild Project or Invalidate Caches. It's a modern ritual. I now default to my terminal. It's honest. It listens. It doesn't pretend.

Plugin development? A labyrinth. Testing plugins is like chasing asynchronous shadows. Documentation is scarce, SDKs mutate overnight, and the event system reminds me of a toddler with espresso. Thousands of change events for a single file edit. I wanted to build useful tools.

Even giants like AWS and CodePilot plugins throw random exceptions. Testing? What's that? The SDK laughs in JUnit.

The final twist: my own plugin, full of hope and effort, is now the ugliest code I've ever written. I can't fix it. I barely recognize it. I miss simplicity. I miss reliability. I miss fun.

JetBrains still has brilliance. But quality? It's slipping. The warning signs are glowing. Not with malice, but with entropy.

Would be poetic if a new IDE emerged soon. Just like JetBrains once did, fresh, small, efficient. Until then, I'll keep fighting caches, memory bloat, and undetectable test classes… while whispering my Eclipse shortcuts in IntelliJ like ancient spells.

Funny, isn't it? Software today feels less like writing code and more like running a game engine. But the bugs aren't part of the plot. They're just bugs.

#JetBrains #IntelliJ #PluginDevelopment #Java #DeveloperExperience #IDEThoughts #Kotlin #MemoryLeaks #BringBackFun #TerminalNeverLies

N-gated Hacker Newsngate
2025-07-13

🚦 Ah yes, because "Parse, Don't Validate" is totally going to save you from C's foot-gun tendencies. 😂 Let's all pretend that throwing conceptual correctness at C won't lead to a spectacular explosion of memory leaks and buffer overflows! 🔥
lelanthran.com/chap13/content.

N-gated Hacker Newsngate
2025-06-14

🚮 Oh joy, yet another groundbreaking GitHub issue about a "green tea" garbage collector that promises to save the world from memory leaks🍵, if only anyone could stay awake long enough to care. Meanwhile, GitHub Copilot is still trying to figure out what to do with all this hot air♨️ and more security holes than a sieve🔍.
github.com/golang/go/issues/73

N-gated Hacker Newsngate
2025-05-11

Rust devs think ++ is like a horror film where memory leaks are the monster that keeps coming back for sequels nobody wanted. 😂 Meanwhile, C++ devs are proudly riding that memory leak rollercoaster, proving the point with every malloc-mishap! 🎢💥
babaei.net/blog/rust-devs-thin

Tuvoc Technologiestuvoc
2025-03-18

A Complete Guide for Developers to Master Node.js Memory Leaks

vintfint.com/blogs/50289/A-Com

Learn how to identify, debug, and prevent memory leaks in Node.js applications. This guide equips developers with best practices to optimize performance and ensure efficient memory management.










Webdevconwebdevcon
2025-03-03

JavaScript apps running out of memory? 😱 Learn how to detect and fix memory leaks with Daniel Danielecki at !

🔗 webdevcon.nl/session/memory-le

2025-01-27

A quick demonstration of using the State: Overview page in Kitten’s¹ settings while developing to keep an eye on your event and event listener counts to avoid memory leaks.

Notice how the events and listeners counts change as I navigate between the People and Settings pages in my Place² node and that they are consistent. If they were rising as I navigated back and forth I’d know I had a memory leak somewhere.

If you use Kitten’s built-in features (e.g., the `addEventHandler()` method on your `kitten.Component` subclasses, Kitten will handle adding and removing listeners for you automatically during your component’s lifecycle. You can also do so manually in your component’s automatically-called `onConnect()` and `onDisconnect()` event handlers.

This view is useful during development to ensure you don’t have any memory leaks as pages are loaded and unloaded.

vimeo.com/1050714714

¹ kitten.small-web.org
² Place is in early development at the moment (codeberg.org/place/app)

#Kitten #SmallWeb #SmallTech #demo #developerExperience #developerTools #design #eventModel #events #memory #memoryLeaks #observerPattern #listeners #web #dev #HTML #CSS #JavaScript #NodeJS #server #platform #framework #WebSockets #hypermedia #htmx #StreamingHTML #place #peerToPeer #peerToPeerWeb

Erik JonkerErikJonker
2024-11-10
Michael van Niekerk 🦀 ☕️ ⚛mvniekerk@techhub.social
2024-10-24

PSA: If you're writing a #WASM plugin for #Envoy / #Istio, and you're using the built-in K/V store in Envoy, then your plugin will choke up.

And the great thing is it doesn't choke up immediately. MTTF ±22 days.

#memoryleaks

Kevin Karhan :verified:kkarhan@infosec.space
2024-03-05

@ldubost shit like #aws or any #Cloud incentivie #WastefulComputing by making it too cheap and easy to throw computational resources onto shit code...

Instead of forcing software vendors & devs to fix #MemoryLeaks, people just buy add more RAM...

LunarSpaceDaniTheRealDanini
2024-01-15

@kkarhan@social.tchncs.de @lamp
Pretty much.. not to mention the recent corpo additions to the game, adding their own version of vbucks that doesn’t really do anything other then exist. And the recent tos and eula changes that explain how much they don’t care about your .

With bad and poor optimization especially in a game they should have focused on improving quality, but I don’t expect that these days from such a corpo game company

2023-12-16

Nice summary of the most common #memoryLeaks in #Android. If you are experiencing OOMs and not sure where they are coming, review the usage of these examples in your code.

medium.com/@dugguRK/top-10-and

Code with the Italians 🤌codewiththeitalians@androiddev.social
2023-12-02

🐦 LeakCanary demystified! Join us and Pierre-Yves Ricau for an in-depth exploration of this essential Android tool. Don't miss out: youtu.be/ZdZSGnJw3mY #MemoryLeaks #AndroidProgramming

Code with the Italians 🤌codewiththeitalians@androiddev.social
2023-11-28

🚨 Tomorrow's episode is a must-watch for #AndroidDev enthusiasts! 🚀 Join us as Pierre-Yves Ricau dives into LeakCanary, the essential tool for detecting memory leaks in Android apps. Stay ahead of the curve!
👉 Tune in: cwti.link/live
#MemoryLeaks #LeakCanary

Peter N. M. Hansteenpitrh
2023-10-24

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst