ODM 3.0.3 bug report

Looks like ODM is pulling a new 3.0.3 version that is breaking when generating texturing.

    {
        "command": "\"/code/SuperBuild/install/bin/texrecon\" \"/datasets/code/opensfm/undistorted/reconstruction.nvm\" \"/datasets/code/odm_meshing/odm_25dmesh.ply\" \"/datasets/code/odm_texturing_25d/odm_textured_model_geo\" -d gmi -o gauss_clamping -t none --no_intermediate_results    --nadir_mode  --max_texture_size=24576 ",
        "exitCode": 137,
        "output": [
            "1\t206008",
            "2\t205983",
            "2\t205973",
            "2\t205963",
            "2\t205959",
            "2\t205956",
            "142771 faces have not been seen",
            "Took: 27.684s",
            "Generating texture patches:",
            "Running... Killed"
        ]
    }
],
"success": false,
"error": {
    "code": 137,
    "message": "Child returned 137"
},
"stackTrace": [
    "Traceback (most recent call last):",
    "File \"/code/stages/odm_app.py\", line 81, in execute",
    "self.first_stage.run()",
    "File \"/code/opendm/types.py\", line 386, in run",
    "self.next_stage.run(outputs)",
    "File \"/code/opendm/types.py\", line 386, in run",
    "self.next_stage.run(outputs)",
    "File \"/code/opendm/types.py\", line 386, in run",
    "self.next_stage.run(outputs)",
    "[Previous line repeated 4 more times]",
    "File \"/code/opendm/types.py\", line 365, in run",
    "self.process(self.args, outputs)",
    "File \"/code/stages/mvstex.py\", line 121, in process",
    "system.run('\"{bin}\" \"{nvm_file}\" \"{model}\" \"{out_dir}\" '",
    "File \"/code/opendm/system.py\", line 109, in run",
    "raise SubprocessException(\"Child returned {}\".format(retcode), retcode)",
    "opendm.system.SubprocessException: Child returned 137",
    ""
],
"endTime": "2023-01-11T16:22:19.693270",
"totalTime": 6425.22
1 Like

Quick update, not sure why but this issue seems to only happening when I use the triangulation flag (which previously worked fine). Looks like a memory leak as the texturing process slowly eats through 160 GB RAM and almost the same amount of swap until it crashes. Dataset had 88 photos, 45M each, 80/70 overlap.

1 Like

Are you able to share the dataset, log, parameters, etc in an Issue on our GitHub?

Yes I should be able to do that. The dataset is in blog storage, so easier to share via email to someone with an Azure account. Otherwise I can upload elsewhere and share.

1 Like

Issue opened

3.0.3 texturing runs up memory until it fails, only when using triangulation · Issue #1585 · OpenDroneMap/ODM (github.com)

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.