fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

8.8K
active users

#memoryleak

0 posts0 participants0 posts today
.:\dGh/:.<p>Does someone knows a way to test or diagnose a PHP process for memory leaks?</p><p>Asking for a friend. He puts NGINX with PHP and after a while a mail comes saying PHP 8.2.5 goes out of memory, good luck.</p><p><a href="https://mastodon.social/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Programming</span></a> <a href="https://mastodon.social/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PHP</span></a> <a href="https://mastodon.social/tags/WebServers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebServers</span></a> <a href="https://mastodon.social/tags/Web" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Web</span></a> <a href="https://mastodon.social/tags/Servers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Servers</span></a> <a href="https://mastodon.social/tags/Debug" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Debug</span></a> <a href="https://mastodon.social/tags/Debugging" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Debugging</span></a> <a href="https://mastodon.social/tags/MemoryLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MemoryLeak</span></a></p>
Lukas Rotermund<p>How do you usually deal with memory leaks in PHP (Symfony)? I juggle in an isolated process with a massive number of data sets that I load in batches via Doctrine, process, and then detach via the entity manager using `clear`, including a call to `gc_collect_cycles`, after unsetting the result array. There aren't any variables that have a reference anymore. The units of work from the entity manager are also empty. But the memory usage keeps going up.</p><p>UPDATE: found the leak in a third party API client 😄</p><p><a href="https://social.tchncs.de/tags/php" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>php</span></a> <a href="https://social.tchncs.de/tags/Doctrine" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Doctrine</span></a> <a href="https://social.tchncs.de/tags/symfony" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>symfony</span></a> <a href="https://social.tchncs.de/tags/MemoryLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MemoryLeak</span></a></p>
N-gated Hacker News<p>🚨 OMG, look! Another digital disaster discovered by self-proclaimed "Binarly REsearch" saviors! 😱 Yet another Secure Boot <a href="https://mastodon.social/tags/bypass" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bypass</span></a> - who'd have thought it?! 🙄 Apparently, a memory leak is a bigger deal than our morning coffee spill. ☕📉<br><a href="https://www.binarly.io/blog/another-crack-in-the-chain-of-trust" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">binarly.io/blog/another-crack-</span><span class="invisible">in-the-chain-of-trust</span></a> <a href="https://mastodon.social/tags/digitaldisaster" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>digitaldisaster</span></a> <a href="https://mastodon.social/tags/SecureBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SecureBoot</span></a> <a href="https://mastodon.social/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a> <a href="https://mastodon.social/tags/memoryleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>memoryleak</span></a> <a href="https://mastodon.social/tags/BinarlyResearch" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BinarlyResearch</span></a> <a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HackerNews</span></a> <a href="https://mastodon.social/tags/ngated" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ngated</span></a></p>
Stuart Longland (VK4MSL)<p>The Mastodon web client is one of the best ways I've experienced for interaction with Mastodon itself on a generic Linux machine, but blimey, does it have a memory leak!</p><p>Left it open on my laptop, it has gobbled about 48% of system RAM according to `top`'s %MEM column (not sure if this includes swap).</p><p>The machine has 8GB RAM and 32GB swap. It took 10 minutes for Firefox to react to a close instruction.</p><p>It usually starts consuming lots of memory after 6 hours of observing the main feed: the problem is much worse if viewing videos (silent "GIF"s or otherwise).</p><p>(cc <span class="h-card" translate="no"><a href="https://mastodon.social/@Mastodon" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Mastodon</span></a></span>)</p><p><a href="https://mastodon.longlandclan.id.au/tags/Bug" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Bug</span></a> <a href="https://mastodon.longlandclan.id.au/tags/MemoryLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MemoryLeak</span></a></p>
Wilda Software<p>Można by było myśleć, że czasy wycieków pamięci to zapomniany rozdział w programowaniu, ale nic bardziej mylnego - nadal ten problem się pojawia i istnieje potrzeba, aby go badać. Tutaj autor pokazuje, jak można to robić w aplikacjach napisanych w Node.js.</p><p><a href="https://mastodon.social/tags/NodeJS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NodeJS</span></a> <a href="https://mastodon.social/tags/MemoryLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MemoryLeak</span></a> <a href="https://mastodon.social/tags/Programowanie" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Programowanie</span></a></p><p><a href="https://dev.to/gkampitakis/tracking-down-high-memory-usage-in-nodejs-2lbn" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dev.to/gkampitakis/tracking-do</span><span class="invisible">wn-high-memory-usage-in-nodejs-2lbn</span></a></p>
9Lukas5 🚂 🐧<p>Nach Null setzen der Klassenvariablen in der tearDown() die die Referenzen hatten gehen die Zähler auch wieder runter und der scheiß fliegt mir nicht mehr um die Ohren 🙌🏼</p><p><a href="https://mastodontech.de/tags/workleaks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>workleaks</span></a> <a href="https://mastodontech.de/tags/MemoryLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MemoryLeak</span></a> <a href="https://mastodontech.de/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Python</span></a> <a href="https://mastodontech.de/tags/Java" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Java</span></a> <a href="https://mastodontech.de/tags/Unittest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Unittest</span></a></p>
9Lukas5 🚂 🐧<p>Damit bleiben natürlich auch diese Instanzen referenziert und werden nicht aufgeräumt. </p><p>Mit wachsender Anzahl Testklassen, werdens also auch immer mehr Referenzen die unnötig weiter Platz belegen und 🤯</p><p>Hab die Theorie dann eben mal überprüft, indem ich in Kon-/Destruktor der instanziierten Klassen einen Zähler gepackt hab.<br>Und recht gehabt.</p><p><a href="https://mastodontech.de/tags/workleaks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>workleaks</span></a> <a href="https://mastodontech.de/tags/MemoryLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MemoryLeak</span></a> <a href="https://mastodontech.de/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Python</span></a> <a href="https://mastodontech.de/tags/Java" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Java</span></a> <a href="https://mastodontech.de/tags/Unittest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Unittest</span></a></p>
9Lukas5 🚂 🐧<p>Ich hab mittlerweile so viele Unittests in dieser Suite drin, der VM HeapSpace fliegt mir um die Ohren 😶‍🌫️<br>Heute morgen also mal Speicheroptimierung in den Unittests betrieben :blobcatverified: </p><p>Was war passiert?<br>Naja, ich hab in der setUp() 9 Objekte instanziiert und in Klassenvariablen der Testklasse abgelegt.</p><p>Well, am Ende des Tests, hält die Testumgebung die Referenz auf alle Testklassen bis sie mit allem fertig ist, für final Reporting. 👀</p><p><a href="https://mastodontech.de/tags/workleaks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>workleaks</span></a> <a href="https://mastodontech.de/tags/MemoryLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MemoryLeak</span></a> <a href="https://mastodontech.de/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Python</span></a> <a href="https://mastodontech.de/tags/Java" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Java</span></a> <a href="https://mastodontech.de/tags/Unittest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Unittest</span></a></p>
Random Magic<p><a href="https://mastodon.social/tags/magicthegathering" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>magicthegathering</span></a> <a href="https://mastodon.social/tags/mtg" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mtg</span></a> <a href="https://mastodon.social/tags/MemoryLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MemoryLeak</span></a> <a href="https://mastodon.social/tags/KarlKopinski" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>KarlKopinski</span></a></p>
Marine Tachibana<p>The object I instantiated inside of a loop never gets garbage collected. </p><p>sample:</p><p>for(1000times){<br> SomeObject obj = new SomeObject();<br>}</p><p>What could be a culprit?</p><p>BTW, SomeObject is a stupidly large class which I don’t fully understand what is inside of it. </p><p><a href="https://mas.to/tags/java" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>java</span></a> <a href="https://mas.to/tags/question" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>question</span></a> <a href="https://mas.to/tags/bug" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bug</span></a> <a href="https://mas.to/tags/memoryleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>memoryleak</span></a></p>
MetalSnake<p>I have a very weird memory bug in python or QT6. I add a few thousand rows to a QTableWidget. That works just fine, but if I first move the window, and then add the rows it takes a long time and memory usage goes over 40gb. <br>And it triggers only on the Mac I'm developing on. Other Mac with the same OS version, same python version has no problem. <br>On the dev Mac I tried different python3 version, created a new venv, but nothing helps. <br>tracemalloc doesn't seem to see the huge memory usage. <br>Any ideas on how to find the cause of this? I'm out of ideas. </p><p><a href="https://oldbytes.space/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>python</span></a> <a href="https://oldbytes.space/tags/qt6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>qt6</span></a> <a href="https://oldbytes.space/tags/memoryleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>memoryleak</span></a> <a href="https://oldbytes.space/tags/debugging" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>debugging</span></a></p>
Techy Geek :verified:<p>🚨 **<a href="https://infosec.exchange/tags/Kodi21" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kodi21</span></a> users beware!** A memory leak bug is affecting systems with prolonged uptime (1-2 days). Rebooting temporarily resolves the issue, but it returns. This occurs even with sufficient memory. Testing on **<a href="https://infosec.exchange/tags/Debian12" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Debian12</span></a>** with **<a href="https://infosec.exchange/tags/RaspberryPi5" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RaspberryPi5</span></a>** running **<a href="https://infosec.exchange/tags/KodiMediaCenter" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>KodiMediaCenter</span></a> 21.1** reveals persistent problems. </p><p>Stay updated and monitor your systems! </p><p><a href="https://infosec.exchange/tags/Kodi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kodi</span></a> <a href="https://infosec.exchange/tags/MemoryLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MemoryLeak</span></a> <a href="https://infosec.exchange/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RaspberryPi</span></a> <a href="https://infosec.exchange/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a></p><p><a href="https://forum.kodi.tv/showthread.php?tid=379280" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">forum.kodi.tv/showthread.php?t</span><span class="invisible">id=379280</span></a></p>
Axel Leroy<p>Oops, someone left a memory leak in their self-checkout software<br><a href="https://toot.community/tags/Java" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Java</span></a> <a href="https://toot.community/tags/MemoryLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MemoryLeak</span></a> <a href="https://toot.community/tags/ErrorInTheWild" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ErrorInTheWild</span></a></p>
Paula Penedo 💜🖤<p>A project I’m working on with Next.js is having serious memory leak issues. Prod clusters have a constant spike of memory usage until it drops because the machine restarts. 3h tops until the server restarts itself.</p><p>Not using next/image, version 14.3, using app router. </p><p><a href="https://mastodon.social/tags/nextjs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nextjs</span></a> <a href="https://mastodon.social/tags/memoryLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>memoryLeak</span></a> <a href="https://mastodon.social/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>javascript</span></a></p>
Inautilo<p><a href="https://mastodon.social/tags/Development" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Development</span></a> <a href="https://mastodon.social/tags/Techniques" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Techniques</span></a><br>Common causes of memory leaks in JavaScript · Resolving memory leaks in Node.js and Deno applications <a href="https://ilo.im/15zrzu" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">ilo.im/15zrzu</span><span class="invisible"></span></a></p><p>_____<br><a href="https://mastodon.social/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Programming</span></a> <a href="https://mastodon.social/tags/Debugging" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Debugging</span></a> <a href="https://mastodon.social/tags/Profiling" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Profiling</span></a> <a href="https://mastodon.social/tags/MemoryLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MemoryLeak</span></a> <a href="https://mastodon.social/tags/JavaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JavaScript</span></a> <a href="https://mastodon.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebDev</span></a> <a href="https://mastodon.social/tags/Backend" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Backend</span></a> <a href="https://mastodon.social/tags/NextJS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NextJS</span></a> <a href="https://mastodon.social/tags/Deno" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Deno</span></a></p>
kalvn<p>Méfiez-vous des objets créés dans le scope global. Ils peuvent très rapidement constituer un memory leak.</p><p>Common Causes of Memory Leaks in JavaScript | Trevor Indrek Lasn<br><a href="https://www.trevorlasn.com/blog/common-causes-of-memory-leaks-in-javascript" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">trevorlasn.com/blog/common-cau</span><span class="invisible">ses-of-memory-leaks-in-javascript</span></a></p><p><a href="https://mastodon.xyz/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>javascript</span></a> <a href="https://mastodon.xyz/tags/astuce" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>astuce</span></a> <a href="https://mastodon.xyz/tags/m%C3%A9moire" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mémoire</span></a> <a href="https://mastodon.xyz/tags/memoryleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>memoryleak</span></a></p>
Tim ☑️ 🔭🌃📷🚴🌳<p>TFW your bug report is the leading cause of a new release version... They only went and fixed it for me. :)</p><p><a href="https://mastodon.online/tags/DxO" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DxO</span></a> <a href="https://mastodon.online/tags/photography" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>photography</span></a> <a href="https://mastodon.online/tags/geek" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>geek</span></a> <a href="https://mastodon.online/tags/win" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>win</span></a> <a href="https://mastodon.online/tags/DxOPhotoLab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DxOPhotoLab</span></a> <a href="https://mastodon.online/tags/memoryleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>memoryleak</span></a> <a href="https://mastodon.online/tags/happiness" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>happiness</span></a></p>
LINUXexpert.org<p>CrowdStrike has had a history of releasing software updates that have inadvertently caused significant disruptions to operating systems, including Linux, Windows, and macOS. These incidents have raised concerns within the IT and cybersecurity communities about the reliability and testing procedures of CrowdStrike’s software releases.<br><a href="https://linuxexpert.org/crowdstrikes-history-of-releasing-software-that-breaks-operating-systems/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">linuxexpert.org/crowdstrikes-h</span><span class="invisible">istory-of-releasing-software-that-breaks-operating-systems/</span></a><br><a href="https://mastodon.social/tags/CrowdStrike" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CrowdStrike</span></a> <a href="https://mastodon.social/tags/Cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Cybersecurity</span></a> <a href="https://mastodon.social/tags/SoftwareUpdates" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareUpdates</span></a> <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://mastodon.social/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Windows</span></a> <a href="https://mastodon.social/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>macOS</span></a> <a href="https://mastodon.social/tags/KernelPanic" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>KernelPanic</span></a> <a href="https://mastodon.social/tags/BSOD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BSOD</span></a> <a href="https://mastodon.social/tags/MemoryLeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MemoryLeak</span></a> <a href="https://mastodon.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> <a href="https://mastodon.social/tags/CodeReview" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CodeReview</span></a> <a href="https://mastodon.social/tags/Transparency" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Transparency</span></a> s</p>
Henrik Jernevad<p>You go Print Center! You may live a life in the shadow of more prominent apps, but that shouldn't stop you from having 177,10 GB of RAM! Or increasing 0,1 GB per second, for that matter! 😝 <a href="https://mastodon.social/tags/macos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>macos</span></a> <a href="https://mastodon.social/tags/memoryleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>memoryleak</span></a></p>
obrhoff<p>Someone reported memory issues with MusaicFm but it seems to be general problem with the „LegacyScreenSaver“ Process. It seems to leak memory. Is there a fix for it or can you somehow migrate to a new ScreenSaver API under macOS?</p><p><a href="https://github.com/obrhoff/MusaicFM/issues/50" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/obrhoff/MusaicFM/is</span><span class="invisible">sues/50</span></a></p><p><a href="https://chaos.social/tags/macos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>macos</span></a> <a href="https://chaos.social/tags/screensaver" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>screensaver</span></a> <a href="https://chaos.social/tags/memoryleak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>memoryleak</span></a> <a href="https://chaos.social/tags/Xcode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Xcode</span></a> <a href="https://chaos.social/tags/appkit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>appkit</span></a></p>