Skip to content
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

Build script (configure.sh install) fails at PoissonRecon IF RAM is below 16GB #1315

Closed
tteke opened this issue Jul 8, 2021 · 4 comments
Closed

Comments

@tteke
Copy link

tteke commented Jul 8, 2021

How did you install OpenDroneMap? (Docker, natively, ...)?

natively

What's your browser and operating system? (Copy/paste the output of https://www.whatismybrowser.com/)

ubuntu 20.04

What is the problem?

build script fails during the PoissonRecon build step. If the computer has 8GB ram. Build failed it on 2 different computers, then I upgraded ram to 16GB on one of them. The system with 16GB ram system built successfully.

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.

NA

How can we reproduce this? (What steps did you do to trigger the problem? What parameters are you using for processing? If possible please include a copy of your dataset uploaded on Google Drive or Dropbox. Be detailed)

Try building ODM (2.5.7, 2.5.6, 2.5.5 only tried those 3) on a ubuntu 20.04 system with 8GB ram

@pierotofy
Copy link
Member

Noticed that too, we went around it by allocating extra swap. If you have any suggestions on how to improve it, we'd welcome a pull request. This started happening with the newer versions of the PoissonRecon code. Older versions compiled fine with less memory.

@tteke
Copy link
Author

tteke commented Jul 8, 2021

Got it. Maybe I should open an issue on their repo then. Do you know by chance exactly which release started causing the issue ?

@pierotofy
Copy link
Member

Not sure which one; but within the last 2 years if that helps narrow it down 😬

@sbonaime
Copy link
Contributor

same problem as #1679 fix with #1681

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants