Claude Code
performance
Memory Leak in Long-Running Background Job
A background job that runs periodically starts consuming more memory with each execution. After hours of running, the application runs out of memory and crashes. The job itself is correct but something isn't being cleaned up properly.
Memory usage climbs steadily despite the job appearing to complete normally.
Error Messages You Might See
java.lang.OutOfMemoryError: Java heap space
Memory usage climbs to 100% after running job repeatedly
Process killed due to memory limit exceeded
Common Causes
- Large collection (List, Set) accumulating items without clearing
- Event listeners registered but never unregistered, accumulating with each run
- Database connections or file handles not closed in finally block
- Strong references held to completed objects preventing garbage collection
- Timer or scheduled task not cancelled, creating new instances on top of old ones
How to Fix It
Use memory profiler to find memory growth (Java: JProfiler, YourKit). Look for accumulating collections. Ensure resources are closed with try-finally or try-with-resources. Unregister event listeners when done. Clear collections: list.clear(). Check for circular references. Use weak references if needed. Monitor memory: jmap -heap PID
Real developers can help you.
legrab
I'll fill this later
Matthew Butler
Systems Development Engineer @ Amazon Web Services
Milan Surelia
Milan Surelia is a Mobile App Developer with 5+ years of experience crafting scalable, cross-platform apps at 7Span and Meticha. At 7Span, he engineers feature-rich Flutter apps with smooth performance and modern UI. As the Co-Founder of Meticha, he builds open-source tools and developer-focused products that solve real-world problems.
Expertise:
💡 Developing cross-platform apps using Flutter, Dart, and Jetpack Compose for Android, iOS, and Web.
🖋️ Sharing insights through technical writing, blogging, and open-source contributions.
🤝 Collaborating closely with designers, PMs, and developers to build seamless mobile experiences.
Notable Achievements:
🎯 Revamped the Vepaar app into Vepaar Store & CRM with a 2x performance boost and smoother UX.
🚀 Launched Compose101 — a Jetpack Compose starter kit to speed up Android development.
🌟 Open source contributions on Github & StackOverflow for Flutter & Dart
🎖️ Worked on improving app performance and user experience with smart solutions.
Milan is always happy to connect, work on new ideas, and explore the latest in technology.
MFox
Full-stack professional senior engineer (15+years). Extensive experience in software development, qa, and IP networking.
Yovel Cohen
I got a lot of experience in building Long-horizon AI Agents in production, Backend apps that scale to millions of users and frontend knowledge as well.
Basel Issmail
’m a Senior Full-Stack Developer and Tech Lead with experience designing and building scalable web platforms. I work across the full development lifecycle, from translating business requirements into technical architecture to delivering reliable production systems.
My work focuses on modern web technologies, including TypeScript, Angular, Node.js, and cloud-based architectures. I enjoy solving complex technical problems and helping teams turn product ideas and prototypes into working platforms that can grow and scale.
In addition to development, I often collaborate closely with product managers, business analysts, designers, and QA teams to ensure that solutions align with both technical and business goals.
I enjoy working with startups and product teams where I can contribute both as a hands-on engineer and as a technical partner in designing and delivering impactful software.
Nam Tran
10 years as fullstack developer
Franck Plazanet
I am a Strategic Engineering Leader with over 8 years of experience building high-availability enterprise systems and scaling high-performing technical teams. My focus is on bridging the gap between complex technology and business growth.
Core Expertise:
🚀 Leadership: Managing and coaching teams of 15+ engineers, fostering a culture of accountability and continuous improvement.
🏗️ Architecture: Enterprise Core Systems, Multi-system Integration (ERP/API/ETL), and Core Database Structure.
☁️ Cloud & Scale: AWS Expert; architected systems handling 10B+ monthly requests and managing 100k+ SKUs.
📈 Business Impact: Aligning tech strategy with P&L goals to drive $70k+ in monthly recurring revenue.
I thrive on "out-of-the-box" thinking to solve complex technical bottlenecks and am always looking for ways to use automation to improve business productivity.
zipking
I am a technologist and product builder dedicated to creating high-impact solutions at the intersection of AI and specialized markets. Currently, I am focused on PropScan (EstateGuard), an AI-driven SaaS platform tailored for the Japanese real estate industry, and exploring the potential of Archify.
As an INFJ-T, I approach development with a "systems-thinking" mindset—balancing technical precision with a deep understanding of user needs. I particularly enjoy the challenge of architecting Vertical AI SaaS and optimizing Small Language Models (SLMs) to solve specific, real-world business problems. Whether I'm in a CTO-level leadership role or hands-on with the code, I thrive on building tools that turn complex data into actionable value.
Rudra Bhikadiya
I build and fix web apps across Next.js, Node.js, and DBs.
Comfortable jumping into messy code, broken APIs, and mysterious bugs.
If your project works in theory but not in reality, I help close that gap.
You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.
Get HelpFrequently Asked Questions
How to find memory leaks?
Use profiler (JProfiler, YourKit, Chrome DevTools). Take heap dumps before/after memory growth. Compare objects in memory.
How to fix common memory leaks?
Use try-finally for resource cleanup. Unregister listeners: obj.removeEventListener(). Clear collections before reuse: list.clear(). Use weak references for caches.
What's a proper resource cleanup pattern?
try-with-resources (Java 7+): try (Resource r = new Resource()) { use r } (auto-closes). Or try-finally with cleanup in finally block.