#memoryleaks — Public Fediverse posts

So Bjarne Stroustrup, the grand wizard of #C++, has a groundbreaking solution for memory leaks: just email him! 📧 Because, of course, the man who invented C++ has nothing better to do. 😂 Meanwhile, his FAQ pages are updated as frequently as a sloth on vacation. 🦥🔄
https://www.stroustrup.com/bs_faq2.html#memory-leaks #BjarneStroustrup #MemoryLeaks #TechHumor #SlothUpdates #HackerNews #ngated

Bjarne Stroustrup: How do I deal with memory leaks? (2022)

https://www.stroustrup.com/bs_faq2.html#memory-leaks

#HackerNews #BjarneStroustrup #MemoryLeaks #C++Programming #SoftwareDevelopment #HackerNews

@visuallyperfect MAX как кейс: типичные баги, архитектурные провалы и почему это закономерно

Если отбросить маркетинг и смотреть на MAX как на инженерный продукт, то картина довольно прозрачная: перед нами типичный “быстро собранный мессенджер”, который пытаются масштабировать раньше, чем он стал устойчивым.

Разберём по слоям.

---

1. Доставка сообщений: не гарантия, а вероятность

Симптоматика знакома: — сообщения приходят пачками
— дублируются
— часть переписки просто исчезает

Это классический признак плохо настроенной eventual consistency. Судя по поведению, backend не обеспечивает строгую гарантию доставки (at-least-once / exactly-once), а плавает где-то между retry-логикой и race conditions.

Что это значит на практике: — повторная отправка → дубликаты
— сбой на клиенте → рассинхрон
— reconnect → “догоняющие” сообщения

Если система не умеет детерминированно разрешать конфликты — это не баг, это следствие архитектуры.

---

2. Push-уведомления: рассинхрон между слоями

Типичный кейс: — пуш пришёл → сообщения нет
— сообщение есть → пуша нет
— всё приходит через 10–15 минут

Основной подозреваемый — интеграция с Firebase Cloud Messaging.

Но проблема глубже: — нет единого источника истины (source of truth)
— пуш и сообщение живут в разных транзакционных контекстах
— отсутствует нормальная idempotency

В нормальной системе push — это просто триггер, а не отдельная сущность с собственной логикой.

---

3. Клиент: UI как узкое место

Фризы, дерганый скролл, зависания — это не “мелкие баги”, это сигнал:

— список сообщений плохо виртуализирован
— перерасчёт layout идёт на основном потоке
— есть memory leaks

Типичный стек-проблем: — RecyclerView захлёбывается на больших чатах
— битмапы не освобождаются
— кеширование сделано “на глаз”

В результате: UI начинает быть bottleneck быстрее, чем сеть.

---

4. Медиа: слабое место всех “быстрых” мессенджеров

Симптомы: — фото не уходят
— видео ломается
— загрузка зависает

Это почти всегда: — нестабильный upload (chunking / retry)
— проблемы на CDN
— отсутствие контроля целостности

Если нет нормального pipeline: encode → upload → verify → deliver
— медиа будет ломаться системно.

---

5. Сессии и авторизация

Самый раздражающий класс багов: — выкидывает из аккаунта
— слетает история
— “переавторизуйтесь”

Это почти гарантированно: — проблемы с токенами
— гонки при обновлении сессии
— рассинхрон между клиентом и сервером

Если auth не атомарен — вся система начинает вести себя хаотично.

---

6. Краши и память

Если приложение: — падает при отправке файлов
— жрёт RAM
— умирает в фоне

значит: — lifecycle не контролируется
— ресурсы не освобождаются
— тестирование на edge-кейсах отсутствует

Это не “надо допилить” — это долг на уровне архитектуры клиента.

---

7. Безопасность: отсутствие ясной модели

Ключевой вопрос — не “есть ли шифрование”, а: кто контролирует ключи и где происходит дешифровка?

Если нет прозрачной end-to-end модели, как у Signal, то: — сервер потенциально видит всё
— безопасность декларативная

Даже Telegram с его спорной моделью MTProto выглядит более зрелым решением на фоне MAX.

---

8. Масштабирование: система не держит нагрузку

Периодические “падения” — это не случайность.

Это означает: — нет горизонтального масштабирования
— нет нормального load balancing
— система не тестировалась под реальную нагрузку

Типичная ошибка: сначала релиз → потом попытка масштабировать → потом firefighting.

---

Итог

MAX — не “глючный мессенджер”.

MAX — это: — backend без строгих гарантий
— клиент без оптимизации
— инфраструктура без запаса прочности

Все наблюдаемые баги — не случайные. Они логично следуют из архитектурных решений.

---

Почему это важно

Такие системы создают ложное ощущение стабильности: пока нагрузка низкая — “вроде работает”.

Но при росте: — баги становятся нормой
— доверие падает
— продукт превращается в технический долг

---

Коротко

Если описать одной строкой:

MAX сейчас — это не продукт уровня production-grade мессенджера, а MVP, который по ошибке выпустили в массовое использование.

---

Если нужно, могу разобрать: — как бы выглядела нормальная архитектура такого мессенджера
— или сравнить MAX с WhatsApp / Signal / Telegram на уровне протоколов и backend-дизайна

#MAX
#Мессенджеры
#Инженерия
#SoftwareEngineering
#Backend
#DistributedSystems
#EventualConsistency
#MessageQueues
#PushNotifications
#FCM
#AndroidDev
#MobileDev
#UX
#Performance
#MemoryLeaks
#Scalability
#Reliability
#HighLoad
#DevOps
#Microservices
#CDN
#Security
#EndToEndEncryption
#Signal
#Telegram
#ITАнализ

Heap dumps are not just debugging artifacts.

They are full memory snapshots. That means passwords, API tokens, and PII in plain text.

In this hands-on guide, I show how to detect and redact sensitive data from .hprof files using hprof-redact — without breaking memory analysis.

If you ever share heap dumps, read this first.

https://www.the-main-thread.com/p/java-heap-dump-redact-sensitive-data-hprof

#Java #JVM #Security #DevOps #MemoryLeaks

#WhatsApp has rewritten its media handling library in #RustLang!

The result❓ The codebase dropped from 160,000 lines of C++ to 90,000 while adding robust memory safety protections.

Running on billions of devices - Android phones, iPhones, desktops, watches, and web browsers - this marks one of the largest client-side Rust deployments to date.

Find out more: https://bit.ly/4tv205g

#SoftwareDevelopment #SoftwareSecurity #MemoryLeaks #InfoQ

🚨 Oh great, another #Python 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. 🕵️‍♂️🔍
https://gmpy.dev/blog/2025/psutil-heap-introspection-apis #MemoryLeaks #Cextensions #TechHumor #DeveloperLife #HackerNews #ngated

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. 🚀
https://medium.com/graalvm/writing-truly-memory-safe-jit-compilers-f79ad44558dd #bugfreeJIT #memorysafety #MikeHearn #digitalarmor #memoryleaks #techadventure #HackerNews #ngated

🎉 Wow, #Go added #Valgrind support! Now you can safely ignore memory leaks while you try to remember why you enabled #JavaScript just to read about it. 🙄🔍
https://go-review.googlesource.com/c/go/+/674077 #support #memoryleaks #HackerNews #HackerNews #ngated

OOMProf: Because nothing says "cutting-edge" like watching your program crash in high resolution! 🖥️💥 Let's pretend #eBPF is the savior we didn't know we needed for those oh-so-mysterious memory leaks. 🙄🔍
https://www.polarsignals.com/blog/posts/2025/08/13/oomprof #OOMProf #MemoryLeaks #TechInnovation #CrashResolution #HackerNews #ngated

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

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

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

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

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

🚦 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! 🔥
https://www.lelanthran.com/chap13/content.html #CProgramming #MemoryLeaks #BufferOverflows #SoftwareDevelopment #HackerNews #ngated

🚮 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🔍.
https://github.com/golang/go/issues/73581 #GitHubIssues #GreenTea #GarbageCollector #MemoryLeaks #GitHubCopilot #HackerNews #ngated

🚮 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🔍.
https://github.com/golang/go/issues/73581 #GitHubIssues #GreenTea #GarbageCollector #MemoryLeaks #GitHubCopilot #HackerNews #ngated

🚮 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🔍.
https://github.com/golang/go/issues/73581 #GitHubIssues #GreenTea #GarbageCollector #MemoryLeaks #GitHubCopilot #HackerNews #ngated

🚮 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🔍.
https://github.com/golang/go/issues/73581 #GitHubIssues #GreenTea #GarbageCollector #MemoryLeaks #GitHubCopilot #HackerNews #ngated

Rust devs think #C++ 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! 🎢💥
https://www.babaei.net/blog/rust-devs-think-we-are-hopeless-lets-prove-them-wrong-with-cpp-memory-leaks/ #Rust #memoryleaks #programminghorror #developerhumor #codinglife #HackerNews #ngated

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

https://vintfint.com/blogs/50289/A-Complete-Guide-for-Developers-to-Master-Node-js-Memory

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.

#Nodejs
#MemoryLeaks
#WebDevelopment
#NodejsPerformance
#CodingTips
#JavaScript
#BackendDevelopment
#SoftwareEngineering
#PerformanceOptimization
#DevTips

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

https://vintfint.com/blogs/50289/A-Complete-Guide-for-Developers-to-Master-Node-js-Memory

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.

#Nodejs
#MemoryLeaks
#WebDevelopment
#NodejsPerformance
#CodingTips
#JavaScript
#BackendDevelopment
#SoftwareEngineering
#PerformanceOptimization
#DevTips

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

https://vintfint.com/blogs/50289/A-Complete-Guide-for-Developers-to-Master-Node-js-Memory

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.

#Nodejs
#MemoryLeaks
#WebDevelopment
#NodejsPerformance
#CodingTips
#JavaScript
#BackendDevelopment
#SoftwareEngineering
#PerformanceOptimization
#DevTips

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

https://vintfint.com/blogs/50289/A-Complete-Guide-for-Developers-to-Master-Node-js-Memory

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.

#Nodejs
#MemoryLeaks
#WebDevelopment
#NodejsPerformance
#CodingTips
#JavaScript
#BackendDevelopment
#SoftwareEngineering
#PerformanceOptimization
#DevTips

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

https://vintfint.com/blogs/50289/A-Complete-Guide-for-Developers-to-Master-Node-js-Memory

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.

#Nodejs
#MemoryLeaks
#WebDevelopment
#NodejsPerformance
#CodingTips
#JavaScript
#BackendDevelopment
#SoftwareEngineering
#PerformanceOptimization
#DevTips

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.

https://vimeo.com/1050714714

¹ https://kitten.small-web.org
² Place is in early development at the moment (https://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

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.

https://vimeo.com/1050714714

¹ https://kitten.small-web.org
² Place is in early development at the moment (https://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

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.

https://vimeo.com/1050714714

¹ https://kitten.small-web.org
² Place is in early development at the moment (https://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

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.

https://vimeo.com/1050714714

¹ https://kitten.small-web.org
² Place is in early development at the moment (https://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

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.

https://vimeo.com/1050714714

¹ https://kitten.small-web.org
² Place is in early development at the moment (https://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

I can't program in C or Rust, interesting discussion however.
https://www.theregister.com/2024/11/08/the_us_government_wants_developers/
#coding #Rust #C #memoryleaks

Unlocking the Secrets of Managed Memory: Dive into Event Handler Leak Insights!

#visualstudio #dotnet #debugging #memoryleaks
https://devblogs.microsoft.com/visualstudio/unlocking-the-secrets-of-managed-memory-dive-into-event-handler-leak-insights/

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.

https://medium.com/@dugguRK/top-10-android-memory-leak-causes-9cdd8cbd5489

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

🚨 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

OpenBSD's built-in memory leak detection https://www.undeadly.org/cgi?action=article;sid=20231024064619 #openbsd #malloc #memoryleaks #security

#Deezer führt in drei verschiedenen Browser unter #FreeBSD zu #MemoryLeaks! In #Iridium (basierend auf #Chromium), #Falkon (basierend auf #QtWebEngine) und #Firefox

Es gab bereits früher ein solches Leak in #Firefox unter #Windows, das wurde mittlerweile behoben.

Ist das nur bei mir so?
Liegt das am OS oder an Deezer?

Einen Client für #Deezer für #FreeBSD gibt es leider nicht.

I just found out that it's a good thing I bought a lower end version of my GPU back in the day - at least I get to see firsthand how #AlienHorizon reacts to running out of VRAM.
Spoiler: not very well.
#GameDev #MemoryLeaks

Happy Friday!

The final #blog post of the year is also the last installment of the #MemoryLeaks series, in which I remember the games of my youth. For this final post we're going all the way back to... [checks notes]... 2020 to look at #DeepRockGalactic, the game that took over my life during the pandemic.

http://www.kurtpankau.com/2022/12/memory-leaks-deep-rock-galactic.html

Oh hey, it's Friday. Today's #blog post is the penultimate installment of #MemoryLeaks, in which I remember favorite games. Today we're looking at Super Bomberman.

http://www.kurtpankau.com/2022/12/memory-leaks-super-bomberman.html

Happy Friday, y'all!

Today's #blog post is another installment of #MemoryLeaks in which I fondly remember favorite #VideoGames. Today we look all the way back at... Pokemon Shield.

http://www.kurtpankau.com/2022/12/memory-leaks-pokemon-shield.html

Today's #blog post is another installment of #MemoryLeaks, in which I remember the video games of my childhood Today's re-look is LEFT 4 DEAD 2, a game in which Valve gets close to releasing a sequel with "3" in the title but doesn't quite manage.

http://www.kurtpankau.com/2022/11/memory-leaks-left-4-dead-2.html