XHackStatus
Improvement

XHack AI v2.4.7: Crash Fixes & Resilient Browsing

A major stability update focused on preventing crashes, UI freezes, memory issues, and browser failures. XHack now handles browser engine failures automatically, respects your selected engine, improves memory protection, and ships a signed and notarized macOS installer.

XHack AI v2.4.7

Release date: October 6, 2026 Status: Critical stability update

XHack AI v2.4.7 is a major stability release focused on making long-running browsing and security tasks more reliable.

This release addresses several field-reported issues including Windows crashes, UI freezes during long browsing sessions, excessive memory usage, embedded browser memory leaks, and browser engine failures.

Updating to v2.4.7 is strongly recommended.

🚀 What's New

Failsafe Browser Engine Switching

XHack can now automatically recover when a browser engine fails to launch.

If your selected or preferred engine cannot start, XHack will automatically try another available engine instead of immediately failing the task.

The agent will also report which browser engine was ultimately used.

This means a temporary browser engine failure should no longer leave an entire task stuck or failed.

Your Browser Engine Selection Is Now Respected

Your browser engine selection in Settings is now fully respected.

If you select:

  • Embedded
  • CloakBrowser
  • Playwright

XHack will always try your selected engine first.

The agent can no longer silently override your selection.

If you choose Automatic, XHack can continue selecting the best available engine for the task.

If your selected engine fails to launch, the new failsafe system can still switch to another working engine so the task can continue.

Signed & Notarized macOS Installer

XHack now ships with a proper signed and notarized .dmg installer for macOS.

The new installer provides:

  • Drag-and-drop installation
  • Proper XHack branding
  • Apple code signing
  • Apple notarization
  • Better compatibility with managed and corporate Macs
  • Reduced Gatekeeper installation issues

This makes deploying XHack on managed macOS environments significantly easier.

Smarter Memory Protection

The memory watchdog has been significantly improved.

Previously, memory monitoring focused primarily on the main XHack process. This could miss large amounts of memory consumed by browser renderers and other child processes.

XHack now monitors the entire XHack process tree, including:

  • Built-in browser processes
  • Browser renderers
  • GPU processes
  • Recon child processes
  • Other XHack subprocesses

Memory protection thresholds are also now based on your machine's available RAM rather than relying on fixed limits.

This allows XHack to behave more appropriately on both:

  • RAM-constrained laptops
  • High-memory workstations

🛠️ Stability & Crash Fixes

Fixed UI Freeze During Long Browsing

Fixed an issue where the XHack interface could freeze during long browsing sessions and potentially require the application to be force-quit.

The built-in browser was previously writing request and response captures directly on the UI thread. As the capture log grew, these operations could block the interface.

Capture writes now run away from the UI thread, keeping the application responsive during longer browsing operations.

Fixed Browser Memory Monitoring

The low-memory protection system previously did not fully account for the embedded browser process tree.

A browser session could therefore consume several gigabytes of memory without the watchdog accurately detecting the actual usage.

XHack now calculates memory usage across the complete process tree and can pause the task before memory consumption becomes dangerous.

RAM-Aware Memory Thresholds

Memory thresholds are now calculated relative to your system's RAM.

This provides more appropriate protection across different machines.

For example, an 8 GB laptop and a 64 GB workstation should not be treated as if they have the same memory capacity.

Improved Memory Usage Reporting

The memory warning banner now provides more accurate information.

Depending on the cause of the warning, XHack can report:

  • XHack's actual memory usage in GB
  • System memory utilization percentage

This makes it easier to understand what is causing the memory pressure.

Fixed Embedded Browser Memory Leak

Fixed a memory leak where the embedded browser engine could remain allocated after an agent switched targets or a chat was deleted.

The browser engine is now properly released and reaped, helping long-running and multi-target engagements remain more stable.

Fixed Embedded Browser Screenshot Crash

Hardened the embedded browser screenshot functionality against a rare native crash that could occur under heavy load.

Fixed Windows Stealth Browser Crash

Fixed a Windows crash caused by the stealth browser's background update check.

The automatic background updater has been disabled to prevent this crash.

The browser engine can still be installed on demand when it is actually required.

Improved Browser Failure Recovery

Browser launch failures are now handled more gracefully.

XHack will:

  1. Try your configured engine first.
  2. Detect if the engine fails to launch.
  3. Automatically attempt another available engine.
  4. Continue the task when a working engine is available.
  5. Report which engine was ultimately used.

Only when all available browser engines fail will the browser action return an error.

📦 Platform Versions

| Platform | Version | |---|---| | Windows | 2.4.7 | | macOS | 2.4.7 | | macOS Apple Silicon | 2.4.7 | | Linux | 2.4.7 |

⚠️ Important

This is a critical stability update.

If you regularly use XHack for long-running browser tasks, multi-target engagements, reconnaissance, or other resource-intensive workflows, updating to v2.4.7 is strongly recommended.

Download the latest version: https://xhack.io/install

XHack AI v2.4.7 is focused on one thing: keeping your security workflows running reliably, even when individual browser engines, memory usage, or long-running operations become problematic.