Tag: Memory Leaks

Ajax

AJAX: Use Fetch with Signal to Cancel Requests When User Navigates Away

- - ErcanOPAK comment on AJAX: Use Fetch with Signal to Cancel Requests When User Navigates Away

User navigates away but old fetch requests keep running in background. Cancel them properly with AbortController. Setup: const controller = new AbortController(); fetch(‘/api/data’, { signal: controller.signal }) .then(response => response.json()) .then(data => console.log(data)) .catch(error => { if (error.name === ‘AbortError’) { console.log(‘Request cancelled’); } }); // Cancel when user leaves page window.addEventListener(‘beforeunload’, () => { […]

Read More
JavaScript

JavaScript Fetch API Secret: How AbortController Stops Memory Leaks in Single Page Apps

- - ErcanOPAK comment on JavaScript Fetch API Secret: How AbortController Stops Memory Leaks in Single Page Apps

Single Page Applications leaking memory from unfinished fetch requests? AbortController is your solution to clean up abandoned API calls. The Memory Leak Problem: // Common React/Vue pattern causing leaks async function fetchUserData(userId) { const response = await fetch(`/api/users/${userId}`); const data = await response.json(); setUserData(data); // State update } // User clicks between tabs quickly: // […]

Read More
Asp.Net Core / C#

.NET Core: Fix Memory Leaks by Understanding IDisposable and Using Patterns

- - ErcanOPAK comment on .NET Core: Fix Memory Leaks by Understanding IDisposable and Using Patterns

Your .NET application’s memory usage grows infinitely? You’re probably not disposing resources properly. Here’s the complete guide. The Memory Leak – Classic Example: // WRONG: Memory leak public async Task ProcessOrdersAsync() { var dbContext = new ApplicationDbContext(); var orders = await dbContext.Orders.ToListAsync(); // Process orders… // dbContext never disposed = connection stays open = memory […]

Read More