ileapp 2026-3.2-dev hanging on artifacts in FFS for iphone 11 ios 26.5.2

[jslorencz]

Hello,
The processing keeps failing at certain artifacts causing a need to start over and disable the artifact at issue. So far one of the Amazon artifacts caused an issue. On the second run web kit cache records caused a failure. Third run fs cache data caused a failure. Each failure causes the program to hang on the artifact. If you click anywhere in the GUI, "Not responding appears" forcing the start over. Any ideas on how to avoid these issues? Is there a way to implement a skip of an artifact if it doesn't begin processing so we don't loose time as we work down the list of what will cause a failure?

[abrignoni]

Thanks for the report. What you are seeing is very likely not a hang. The GUI runs processing on the window's own thread, so during long artifacts the window stops repainting and Windows labels it "Not responding" even though processing is still going. The three artifacts you named are the heaviest cache parsers in the tool, and on a full filesystem they can be silent for a good while.

Two suggestions: let it sit and watch Task Manager (busy CPU means it is working) or the output folder growing, and better yet run the command line version (python ileapp.py -t zip -i <extraction> -o <output>), which prints a timestamped line as each artifact starts and finishes and never freezes.

If an artifact truly errors, iLEAPP already logs it and skips to the next one on its own. We ran these exact artifacts against an iPhone 11 and an iOS 26.5.2 full filesystem and they finish in seconds, so if one of yours really sits for hours with no CPU activity, please share the Script Logs folder from the run and roughly how large the extraction is, and we will dig into that artifact.