SphereSfM icon indicating copy to clipboard operation
SphereSfM copied to clipboard

Segmentation fault when merging reconstructions

Open asddsa886 opened this issue 8 months ago • 0 comments

🐞 Describe the bug A segmentation fault (SIGSEGV) occurs when manually merging two sparse models using the model_merge command, after registering images.

Terminal output:

Reconstruction 1

Images: 135 Points: 8253

Reconstruction 2

Images: 83 Points: 8598

Merging reconstructions

*** Aborted at 1747904292 (unix time) try "date -d @1747904292" if you are using GNU date *** PC: @ 0x55e9e0b148c8 colmap::Reconstruction::Merge() *** SIGSEGV (@0x8) received by PID 8168 (TID 0x7f84da576000) from PID 8; stack trace: *** @ 0x7f84dd0d5631 (unknown) @ 0x7f84dbf59420 (unknown) @ 0x55e9e0b148c8 colmap::Reconstruction::Merge() @ 0x55e9e0a40dd0 colmap::RunModelMerger() @ 0x55e9e0a0f273 main @ 0x7f84db746083 __libc_start_main @ 0x55e9e0a1c2be _start 🔁 To Reproduce Steps to reproduce the behavior:

Create two separate sparse reconstructions.

Register images with colmap image_registrator.

Run the following command:

colmap model_merge
--input_path1 path/to/model1
--input_path2 path/to/model2
--output_path path/to/output Observe crash during merging.

✅ Expected behavior Merging should complete without a crash and produce a unified model in the output path.

🖼️ Screenshots Sparse model directories can be provided if needed.

💻 Environment OS: Ubuntu 20.04

COLMAP Version: v3.8 (built from source)

GPU Support: Enabled

asddsa886 avatar May 26 '25 07:05 asddsa886