https://bugs.documentfoundation.org/show_bug.cgi?id=173425
--- Comment #3 from Pavel Řezníček <[email protected]> --- Confirming this still reproduces today (2026-09-29), three weeks after filing, on the same version (LibreOffice 24.2.7.2). Fresh repro cycle, starting from a clean state: 1. `unopkg remove cz.borova18.BusyBeeDiary` -- removed the leftover, unregistered entry from the last attempt. 2. `unopkg list` -- confirmed empty, no deployed extensions. 3. `unopkg add BusyBeeDiary.oxt` -- crashed again with the same exception: ERROR: Exception occurred: C++ code threw St9bad_alloc: std::bad_alloc at ./bridges/source/cpp_uno/gcc3_linux_x86-64/uno2cpp.cxx:243 Notably, the crashed `add` attempt itself left behind a new unregistered entry (`is registered: no`) in the extension registry -- the same kind of stale entry that triggers the crash in the first place. So once this happens once, every subsequent `unopkg add` fails immediately with "already added" (a different, non-crashing error) until that entry is removed again, at which point `add` crashes the same way once more. The bug is self-perpetuating: nothing about a normal `add`/`remove` cycle clears the underlying condition. Happy to attach a fresh gdb backtrace or any other diagnostics if that would help move this out of UNCONFIRMED. -- You are receiving this mail because: You are the assignee for the bug.
