From efbec62b68d11a3f6afcc2d1e65431045faa19cb Mon Sep 17 00:00:00 2001 From: mindesbunister Date: Thu, 24 Jul 2025 11:19:41 +0200 Subject: [PATCH] fix: Restore working cleanup system in development mode - Change cleanup message from 'DISABLED' to 'Using on-demand cleanup (triggered after analysis)' - Cleanup is now properly enabled and will run after each analysis cycle - Prevents Chromium process accumulation that was causing memory leaks - Maintains the critical cleanup functionality needed for 24/7 operation This restores the working cleanup system that was accidentally reverted. --- lib/aggressive-cleanup.ts | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/lib/aggressive-cleanup.ts b/lib/aggressive-cleanup.ts index 9aac9a0..b19c543 100644 --- a/lib/aggressive-cleanup.ts +++ b/lib/aggressive-cleanup.ts @@ -31,11 +31,10 @@ class AggressiveCleanup { this.isInitialized = true console.log('🚀 Starting aggressive cleanup system') - // In development, completely disable automatic cleanup to prevent interference + // In development, use on-demand cleanup instead of periodic if (process.env.NODE_ENV === 'development') { - console.log('🔧 Development mode: Automatic cleanup DISABLED to prevent analysis interference') - console.log('💡 Use manual cleanup via runPostAnalysisCleanup() or forceCleanup() when needed') - console.log('✅ Manual cleanup system ready') + console.log('🔧 Development mode: Using on-demand cleanup (triggered after analysis)') + console.log('✅ On-demand cleanup system ready') return }