Summary

The Flatpak build of decode-orc v1.1.0 crashes during export of a TBC-based project with a C++ std::vector bounds assertion and SIGABRT.

I can reproduce the crash in the Flatpak build when exporting the same project to both:

• H.264 / MP4
• ProRes

However, a local source build from the same Git revision using the documented Nix workflow does not crash and successfully exports the same .orcprj / .tbc.

This suggests the issue is specific to the Flatpak build and/or its runtime/dependency environment rather than the source media itself.

Steps to reproduce

1. Install and run the Flatpak build of decode-orc v1.1.0.
2. Open the attached project:
   /home/jher/laserdiscs/missing-persons/missing-persons.orcprj
3. Export the project to MP4/H.264.
4. Observe the crash.
5. Repeat using ProRes export.
6. Observe the same crash.

Expected behavior

The project should export successfully without crashing, producing the requested output file.

Actual behavior

The Flatpak build crashes during export with a std::vector out-of-range assertion and aborts with SIGABRT.

Example assertion:

/usr/include/c++/14.3.0/bits/stl_vector.h:1143:
std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type)
[with _Tp = short unsigned int; _Alloc = std::allocator<short unsigned int>;
reference = short unsigned int&; size_type = long unsigned int]:
Assertion '__n < this->size()' failed.

Then:

[orc-app] [critical] CRASH DETECTED: SIGABRT (Abort)

Crash bundles were generated for both export attempts.

Environment

OS: Ubuntu Linux 24.04-based system, kernel 6.8.0-106-generic, x86_64

Build/commit:

Flatpak app version: v1.1.0

Flatpak app reports: orc-gui 960afdb-dirty

Git commit corresponding to local source checkout: 960afdb

Tag: v1.1.0

Flatpak runtime: org.kde.Platform/x86_64/6.9

Flatpak crash bundle reports Qt 6.9.3

Component: orc-gui

Additional context

Flatpak details:

ID: io.github.simoninns.decode-orc
Version: v1.1.0
Runtime: org.kde.Platform/x86_64/6.9
Commit: 8a554b1257099d5b6686ca9db3982875fb725463a525ab970a99843847a4abec

I reproduced the crash with both MP4/H.264 and ProRes. The two crash bundles show the same stack offsets inside orc-gui, suggesting the same internal code path is aborting regardless of codec.

Crash bundle files:

crash_bundle_20260314_215855.zip

crash_bundle_20260314_221323.zip

Both crash_info.txt files show the same relevant stack offsets:

# 0 orc-gui(+0x306e14)
# 1 orc-gui(+0x30788c)
# 7 orc-gui(+0x4b878f)
# 8 orc-gui(+0x4b9ca6)
# 9 orc-gui(+0x4b9f6a)
#10 orc-gui(+0x4b28d4)
#11 orc-gui(+0x5be26f)
#12 orc-gui(+0x5c335c)

Important comparison:

The Flatpak build crashes on this project.

A local Nix source build from the same repo revision does not crash and successfully exports the same project.

Working local build path:

nix --extra-experimental-features "nix-command flakes" develop
nix --extra-experimental-features "nix-command flakes" build
nix --extra-experimental-features "nix-command flakes" run .#orc-gui

In the working Nix environment:

orc-gui reports detached-960afdb

Qt reported by the dev environment is 6.8.3

Export completed successfully with:
ChromaSink: Successfully wrote 29634 frames

This suggests the problem may be specific to the Flatpak build/runtime environment rather than the project data itself.

I can attach:

both crash bundles

the .orcprj

the .tbc.json

a log snippet from the successful Nix-built export

crash_bundle_20260314_215855.zip
crash_bundle_20260314_221323.zip

missing-persons-misc-data.zip