Patching AP file in background leads to random freeze

[RV7PR]

Device: Samsung Galaxy S23 Plus (SM-S916B)
Android version: 14
Magisk version name:
Magisk version code: 27006

When I return after a while, the installation log is gone, the back button doesn't respond, the 'save install log' function generates an empty log file, and the patched file is incomplete.

P.S. The reason I want to run it in the background is that it takes a long time to complete. However, if I remember correctly, it used to be much faster in the past. 🤔

magisk_log_2024-08-14T10.27.24.log

[bbcy375]

I encountered a similar issue on my Samsung S10+ (SM-9750 OneUI 4.1):

I tested versions 27005-27008, and patching the boot file took longer than usual (the same result for both the separate boot file and the full AP file), while patching on version 27000 completed in just a few seconds.
When flashing the patched file via Samsung Odin, it got stuck at "Odin File analysis...".
After directly flashing version 27008 through the Magisk app on the phone, the Zygisk Next module failed to load, displaying "[Failed to inject init] Standalone implementation of Zygisk."
The LSPosed module indicated that "SEPolicy was not properly loaded."
The above content was translated using translation software, so please forgive any inaccuracies.

[udaravima]

I encountered a similar issue on my Samsung S10+ (SM-9750 OneUI 4.1):

I tested versions 27005-27008, and patching the boot file took longer than usual (the same result for both the separate boot file and the full AP file), while patching on version 27000 completed in just a few seconds. When flashing the patched file via Samsung Odin, it got stuck at "Odin File analysis...". After directly flashing version 27008 through the Magisk app on the phone, the Zygisk Next module failed to load, displaying "[Failed to inject init] Standalone implementation of Zygisk." The LSPosed module indicated that "SEPolicy was not properly loaded." The above content was translated using translation software, so please forgive any inaccuracies.

I noticed that the peazip in windows unable to open the tar file so I extracted it in WSL (Linux Distro) tar -xvf <filename> and repack it to a tar it is better if we can repack it in windows using peazip or something.

I think issue is in while packing the patches in.