Open John-Nagle opened 3 months ago
Attempt to rerun from the results of the previous run produced the same error message immediately. So it's reproduceable.
Does it work with docker? We no longer support snap. See https://github.com/OpenDroneMap/ODM/issues/1709
I provided the image set. Did it run with a later version of Open Drone Map?
The snap installation is so much simpler than using Docker.
How did you install ODM? (Docker, installer, natively, ...)?
As a snap on Ubuntu 22.04 LTS
Tested the install by running the "brighton beach" test images, which worked.
What is the problem?
Note the number of bytes. Something tried to allocate 66 gigabytes. Memory consumption was only 4GB (on a 32 GB machine) according to the system memory usage graph (attached) up to that point.
What should be the expected behavior? If this is a feature request, please describe in detail the changes you think should be made to the code, citing files and lines where changes should be made, if possible.
Not crashing.
How can we reproduce this? What steps did you do to trigger the problem? If this is an issue with processing a dataset, YOU MUST include a copy of your dataset AND task output log, uploaded on Google Drive or Dropbox (otherwise we cannot reproduce this).
Get the data set here: https://animats.com/sharpview/testdata/ Get the .zip file from the link "Port Babbage 2".
Log: log.json
Console output: falseoomcrash.txt
Memory usage graph while ODM running:
Notes
Open Drone Map was called by:
opendronemap --project-path .
This is a test of impostor generation for a virtual world. Input is a set of roughly 100 images from a flyover. It's an unusual use of ODM, but shouldn't crash it. The images are reasonable looking.It looks like the matching phase went well, but then, 75% through depth matching, something requested an unreasonable amount of memory all at once.