New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scalable pipeline Segmentation Fault #1100
Comments
The depthmaps in question are actually all missing, not malformed. |
pls check the log for the first step to see why some depth-maps were not estimated; I'd appreciate if you can help debugging this |
This is the log of the first command: DensifyPointCloud-2402011542308B498E.log The issues seem to persist, I don't see why they weren't generated. I tried re-running the pipeline overnight (with |
Rerunning the pipeline with
segfaults on the 3rd command (this time with
The last line before the crash is
which likely crashes because depth maps 873 and 875 are missing. Looking over the logs, I don't see anything overtly suspicious for why the depth maps are not created. I'm now going to run |
Digging further, it seems that the
Weirdly enough, the difference is
|
|
Ran MemTest86 to check for RAM issues (possibly corrupting the DMAPs on export), no fails there. |
Rerunning the code on the machine the issue was present on and also on a different one to see if the problem is with the data. |
The errors occur for the same depth maps when run multiple times. |
I'm at a loss for what to try at this point, let me know what I should do if you have any ideas. |
Found a minimal reproducible example. Taking this COLMAP project: 1-colmap-input.zip Using OpenMVS, I ran
The last step crashes with
Simply running Here are all produced logs and files: 3-after-crash.zip |
Describe the bug
Running the steps outlined in the
MvsScalablePipeline.py
yields a segmentation fault.To Reproduce
Running the following commands (after
InterfaceCOLMAP
):DensifyPointCloud scene.mvs --resolution-level 1 --iters 4 --cuda-device -1 --fusion-mode 1
DensifyPointCloud scene.mvs --resolution-level 1 --iters 4 --cuda-device -1 --sub-scene-area 20000000
DensifyPointCloud scene_0000.mvs --resolution-level 1 --iters 4 --cuda-device -1 --dense-config-file Densify.ini -v 3
Densify.ini
contents areOptimize = 0
Step (3) crashes with the following output:
Trying to run the command for other scenes:
scene_0001.mvs
worksscene_0002.mvs
worksscene_0003.mvs
crashes with0 images (0 calibrated) with a total of 0.00 MPixels (-nan MPixels/image)
(probably a different issue, looks like the scene is empty)scene_0004.mvs
worksLooking at what command (2) produces:
suggests that certain depth maps are malformed, which could perhaps be a reason for the issue?
The text was updated successfully, but these errors were encountered: