Additional diagnostic evidence from another machine, collected September 14, 2026. This closely matches MCL-26854: the same launcher core/build, std::bad_function_call, repeated Unzipper-related helper aborts, and a game session that continues normally.
MACHINE / SOFTWARE • Arch Linux x86_64 with Omarchy 4.0.3-1 (a desktop configuration layer), Hyprland 0.56.2-2 / Wayland; current kernel 7.2.3-arch1-3. These OS versions were collected September 14. • CPU: Intel Core i5-14600K, 20 logical CPUs. • GPU: NVIDIA GeForce RTX 4060 Ti (AD106); nvidia-utils 610.57.04-1. • Memory: approximately 32 GB installed (31 GiB reported); 62 GiB swap. No OOM event was found around the investigated crashes. • Launcher core: 3.39.31, commit 865b5652e408aebc2c51f4477b4e3c3d14e843c0. • Native launcher: 2.6.2; bootstrap: 2.1.3; installed Arch package: minecraft-launcher 1:2.1.3-3 (Official Minecraft Launcher). • CEF: 127.3.5+g114ea2a+chromium-127.0.6533.120. • glibc: 2.44+r24+g16be1518495f-1; gcc-libs/libgcc: 16.2.1+r23+gd564253eb6c8-1. • liblauncher.so ELF build ID: 35409dcda3832d27a40ffe22c9553529327ecf18. • minecraft-launcher ELF build ID: 2f91a58a95fa4bafce624f38beebd03105b7e7d0. • Launcher executable: $HOME/.minecraft/launcher/minecraft-launcher. • The representative September 12 session launched Minecraft Java Edition 26.2, using the bundled Java runtime beneath $HOME/.minecraft/runtime/java-runtime-epsilon/. I have not tested the latest pre-release for this report.
FREQUENCY / MATCHING STACKS The system journal contains 304 launcher core-dump entries from September 5–12, 2026. All 304 contain exactly the same six liblauncher.so offsets: 0x1360a3 -> 0x29f2f1 -> 0x29f43d -> 0x29e9c2 -> 0x1e0b06 -> RunLauncher + 0x1b270e.
Eight selected events were cross-checked against the journal (times CEST, UTC+02): September 6 20:47:50 — PID 3742 September 7 10:30:44 — PID 3741 September 7 14:37:11 — PID 4083 September 7 18:28:40 — PID 3893 September 7 20:32:48 — PID 4445 September 8 09:23:14 — PID 4258 September 11 10:38:00 — PID 12251 September 12 20:08:33 — PID 3740 All eight have SIGABRT and the same launcher offsets. Multiple prior core inspections recovered std::bad_function_call; identical journal stacks do not independently establish the exception type in every one of the 304 cores.
REPRESENTATIVE SESSION: SEPTEMBER 12 20:07:32 CEST: launcher opened normally from the desktop. 20:07:41 CEST: Minecraft Java 26.2 starting. 20:08:33–20:08:37 CEST: 16 launcher helper processes aborted; representative PID 3740. The launcher log records 16 requests for --type=utility --utility-sub-type=unzip.mojom.Unzipper during those same seconds. The first two are at 18:08:33.363907652 and 18:08:33.739589764 UTC, and the final request is at 18:08:37.743060068 UTC. Launcher-log timestamps are UTC, two hours behind CEST. Files beneath webcache2/component_crx_cache, AutofillStates, PKIMetadata, and SafetyTips have matching modification times. 21:10:04 CEST: the game ended normally with exit code 0. Game logging continued after the crash burst; no loss of game progress was observed in the evidence.
The recorded argv says zygote, consistent with the inherited-argv caveat in this issue. On this machine, the Unzipper relationship was established by matching the parent's requests and crash timestamps; I have not independently checked the recovered utility-sub-type argument inside this core.
The exception RTTI name recovered from the C++ exception header was St17bad_function_call (std::bad_function_call). For PID 3740, frame 5 preserved the unwind-header pointer in RBX = 0x559f3de8afc0; reading the typeinfo name through header minus 80 yielded that name. The exception object begins at 0x559f3de8afe0, where its vtable pointer is stored. This was a structured exception-header inspection, not a search for arbitrary strings in process memory.
The other three threads (3741, 3743, 3744) were waiting in pthread_cond_timedwait / pthread_cond_wait with libcef.so frames. NVIDIA libraries were mapped, but none appears in the crashing call stack. The exact launcher callback remains unidentified because launcher debug symbols were unavailable.
REPRODUCTION LIMITS AND IMPACT Observed during ordinary launcher/game use; no newly controlled clean-profile reproduction has been performed. This data set adds evidence for Unzipper-related aborts; I am not asserting independent confirmation of DataDecoder failures. No package update coincided with the selected crashes, and launcher binary mtimes were September 5, before these investigated events.
On Omarchy, these otherwise unobtrusive helper failures produce clickable “Process crashed” notifications offering AI diagnosis. Repeated sessions led to eight diagnostic chats on this machine, although the child playing Minecraft could continue playing. After collecting the evidence, we excluded Minecraft from those desktop prompts only. Launcher/game configuration and systemd core capture were not changed, and no cache deletion was used to produce or address these observations.
This appears to be the same failure already tracked here, persisting on Omarchy 4.0.3-1 with launcher core 3.39.31. The additional value is the newer machine environment, exact ELF build IDs, 304 matching journal stacks, and timestamp correlation with component-cache updates. Raw core dumps and full launcher logs are not included because they may contain account/session data and game chat; the diagnostic details above use a redacted home path.
Prepared with AI assistance (Codex) from local journal records, launcher logs, and core-dump investigations.
Kryvoff
Additional diagnostic evidence from another machine, collected September 14, 2026. This closely matches MCL-26854: the same launcher core/build, std::bad_function_call, repeated Unzipper-related helper aborts, and a game session that continues normally.
MACHINE / SOFTWARE
• Arch Linux x86_64 with Omarchy 4.0.3-1 (a desktop configuration layer), Hyprland 0.56.2-2 / Wayland; current kernel 7.2.3-arch1-3. These OS versions were collected September 14.
• CPU: Intel Core i5-14600K, 20 logical CPUs.
• GPU: NVIDIA GeForce RTX 4060 Ti (AD106); nvidia-utils 610.57.04-1.
• Memory: approximately 32 GB installed (31 GiB reported); 62 GiB swap. No OOM event was found around the investigated crashes.
• Launcher core: 3.39.31, commit 865b5652e408aebc2c51f4477b4e3c3d14e843c0.
• Native launcher: 2.6.2; bootstrap: 2.1.3; installed Arch package: minecraft-launcher 1:2.1.3-3 (Official Minecraft Launcher).
• CEF: 127.3.5+g114ea2a+chromium-127.0.6533.120.
• glibc: 2.44+r24+g16be1518495f-1; gcc-libs/libgcc: 16.2.1+r23+gd564253eb6c8-1.
• liblauncher.so ELF build ID: 35409dcda3832d27a40ffe22c9553529327ecf18.
• minecraft-launcher ELF build ID: 2f91a58a95fa4bafce624f38beebd03105b7e7d0.
• Launcher executable: $HOME/.minecraft/launcher/minecraft-launcher.
• The representative September 12 session launched Minecraft Java Edition 26.2, using the bundled Java runtime beneath $HOME/.minecraft/runtime/java-runtime-epsilon/. I have not tested the latest pre-release for this report.
FREQUENCY / MATCHING STACKS
The system journal contains 304 launcher core-dump entries from September 5–12, 2026. All 304 contain exactly the same six liblauncher.so offsets:
0x1360a3 -> 0x29f2f1 -> 0x29f43d -> 0x29e9c2 -> 0x1e0b06 -> RunLauncher + 0x1b270e.
Counts by date:
2026-09-05: 16
2026-09-06: 32
2026-09-07: 64
2026-09-08: 64
2026-09-09: 32
2026-09-10: 16
2026-09-11: 48
2026-09-12: 32
Total: 304.
Eight selected events were cross-checked against the journal (times CEST, UTC+02):
September 6 20:47:50 — PID 3742
September 7 10:30:44 — PID 3741
September 7 14:37:11 — PID 4083
September 7 18:28:40 — PID 3893
September 7 20:32:48 — PID 4445
September 8 09:23:14 — PID 4258
September 11 10:38:00 — PID 12251
September 12 20:08:33 — PID 3740
All eight have SIGABRT and the same launcher offsets. Multiple prior core inspections recovered std::bad_function_call; identical journal stacks do not independently establish the exception type in every one of the 304 cores.
REPRESENTATIVE SESSION: SEPTEMBER 12
20:07:32 CEST: launcher opened normally from the desktop.
20:07:41 CEST: Minecraft Java 26.2 starting.
20:08:33–20:08:37 CEST: 16 launcher helper processes aborted; representative PID 3740.
The launcher log records 16 requests for --type=utility --utility-sub-type=unzip.mojom.Unzipper during those same seconds. The first two are at 18:08:33.363907652 and 18:08:33.739589764 UTC, and the final request is at 18:08:37.743060068 UTC. Launcher-log timestamps are UTC, two hours behind CEST.
Files beneath webcache2/component_crx_cache, AutofillStates, PKIMetadata, and SafetyTips have matching modification times.
21:10:04 CEST: the game ended normally with exit code 0. Game logging continued after the crash burst; no loss of game progress was observed in the evidence.
CORE EVIDENCE: PID 3740
Signal: SIGABRT, si_code SI_TKILL.
Recorded command:
minecraft-launcher --type=zygote --no-sandbox --enable-crash-reporter=, --change-stack-guard-on-fork=enable --enable-chrome-runtime --user-data-dir=$HOME/.minecraft/webcache2 --log-severity=info --launcherui --workdir=$HOME/.minecraft
The recorded argv says zygote, consistent with the inherited-argv caveat in this issue. On this machine, the Unzipper relationship was established by matching the parent's requests and crash timestamps; I have not independently checked the recovered utility-sub-type argument inside this core.
Main thread stack (module-relative offsets for comparison):
#0 libc.so.6 + 0x9a17c
#1 raise (libc.so.6 + 0x3e5d0)
#2 abort (libc.so.6 + 0x25685)
#3 libstdc++.so.6 + 0x9ac54
#4 libstdc++.so.6 + 0xb581a
#5 __cxa_call_terminate (libstdc++.so.6 + 0x9a459)
#6 __gxx_personality_v0 (libstdc++.so.6 + 0xb4ced)
#7 libgcc_s.so.1 + 0x22043
#8 _Unwind_Resume (libgcc_s.so.1 + 0x22b8b)
#9 liblauncher.so + 0x1360a3
#10 liblauncher.so + 0x29f2f1
#11 liblauncher.so + 0x29f43d
#12 liblauncher.so + 0x29e9c2
#13 liblauncher.so + 0x1e0b06
#14 RunLauncher (liblauncher.so + 0x1b270e)
#15 minecraft-launcher + 0x1ba9e0
#16 minecraft-launcher + 0x49ad9
#17 minecraft-launcher + 0x34ec9
#18 libc.so.6 + 0x27781
#19 __libc_start_main (libc.so.6 + 0x278b9)
#20 _start (minecraft-launcher + 0x36bda)
The exception RTTI name recovered from the C++ exception header was St17bad_function_call (std::bad_function_call). For PID 3740, frame 5 preserved the unwind-header pointer in RBX = 0x559f3de8afc0; reading the typeinfo name through header minus 80 yielded that name. The exception object begins at 0x559f3de8afe0, where its vtable pointer is stored. This was a structured exception-header inspection, not a search for arbitrary strings in process memory.
The other three threads (3741, 3743, 3744) were waiting in pthread_cond_timedwait / pthread_cond_wait with libcef.so frames. NVIDIA libraries were mapped, but none appears in the crashing call stack. The exact launcher callback remains unidentified because launcher debug symbols were unavailable.
REPRODUCTION LIMITS AND IMPACT
Observed during ordinary launcher/game use; no newly controlled clean-profile reproduction has been performed. This data set adds evidence for Unzipper-related aborts; I am not asserting independent confirmation of DataDecoder failures. No package update coincided with the selected crashes, and launcher binary mtimes were September 5, before these investigated events.
On Omarchy, these otherwise unobtrusive helper failures produce clickable “Process crashed” notifications offering AI diagnosis. Repeated sessions led to eight diagnostic chats on this machine, although the child playing Minecraft could continue playing. After collecting the evidence, we excluded Minecraft from those desktop prompts only. Launcher/game configuration and systemd core capture were not changed, and no cache deletion was used to produce or address these observations.
This appears to be the same failure already tracked here, persisting on Omarchy 4.0.3-1 with launcher core 3.39.31. The additional value is the newer machine environment, exact ELF build IDs, 304 matching journal stacks, and timestamp correlation with component-cache updates. Raw core dumps and full launcher logs are not included because they may contain account/session data and game chat; the diagnostic details above use a redacted home path.
Prepared with AI assistance (Codex) from local journal records, launcher logs, and core-dump investigations.