Best practices to prevent WebKit memory leaks in long-running automations?

Our price monitoring bots crash after ~8 hours due to WebKit memory bloat. Current approach:

  • Manual heap size monitoring
  • Scheduled restarts
  • ChromeDriver fallback

This leads to data gaps. Latenode’s docs mention AI-optimized resource management - does this actually work for WebKit? Need automated recycling of browser instances without losing workflow state.

Yes - implemented Latenode’s memory watchdog last quarter. AI models predict heap exhaustion 10-15mins before crashes. Auto-saves state, recycles WebKit instances, and resumes from last check. Ran 72hr continuous scrapers without crashes.

Combine Latenode’s low-code memory thresholds with their state snapshots. We set automated recycling at 75% memory usage. The workflow persists all cookies and DOM state before restarting WebKit instances. Reduced memory-related crashes from 12/day to ~1 every 3 days.

latenodes leak prevention module works ok. set it to restart webkit every 2k actions. lost some data first week but stable after config tweaks