From 45482e868de8100d4eeaf27ec44f3f2d0ed4a5e9 Mon Sep 17 00:00:00 2001
From: "Dylan K. Taylor" <dktapps@pmmp.io>
Date: Sun, 15 Dec 2024 20:45:51 +0000
Subject: [PATCH] Fixed AsyncWorker GC not getting re-enabled after memory dump
 async workers still use automatic GC for now. We should probably switch to
 manual GC at some point, but it's not a priority right now.

---
 src/MemoryDump.php | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/src/MemoryDump.php b/src/MemoryDump.php
index 5f721e041..0503f747c 100644
--- a/src/MemoryDump.php
+++ b/src/MemoryDump.php
@@ -33,6 +33,7 @@ use function file_put_contents;
 use function fopen;
 use function fwrite;
 use function gc_disable;
+use function gc_enabled;
 use function get_class;
 use function get_declared_classes;
 use function get_defined_functions;
@@ -66,6 +67,7 @@ final class MemoryDump{
 	public static function dumpMemory(mixed $startingObject, string $outputFolder, int $maxNesting, int $maxStringSize, \Logger $logger) : void{
 		$hardLimit = Utils::assumeNotFalse(ini_get('memory_limit'), "memory_limit INI directive should always exist");
 		ini_set('memory_limit', '-1');
+		$gcEnabled = gc_enabled();
 		gc_disable();
 
 		if(!file_exists($outputFolder)){
@@ -244,6 +246,9 @@ final class MemoryDump{
 		$logger->info("Finished!");
 
 		ini_set('memory_limit', $hardLimit);
+		if($gcEnabled){
+			gc_enable();
+		}
 	}
 
 	/**