Forum

Author Topic: Bad Allocation, Should I continue?  (Read 1967 times)

rexsham

  • Newbie
  • *
  • Posts: 31
    • View Profile
Bad Allocation, Should I continue?
« on: July 03, 2019, 10:09:10 AM »
I have a project running network mode.
The server has 256GB ram and it is fully used now 256GB/256GB
Project status is 88% in building Dense Cloud at this moment

It just fired a "Bad Allocation" message but the node and server seem can continue to progress.

Will there be any damages to the dense cloud if I continue the process?
SHould I terminate or let it continue? It still has 10 hours to wait if I continue, if I know it will fail finally I will stop processing now

Thank you

Alexey Pasumansky

  • Agisoft Technical Support
  • Hero Member
  • *****
  • Posts: 14099
    • View Profile
Re: Bad Allocation, Should I continue?
« Reply #1 on: July 03, 2019, 12:09:57 PM »
Hello rexsham,

I think it may be reasonable to continue only if you extend the amount of virtual memory on the processing node to avoid "not enough memory" ("bad allocation") error again.

To reduce the memory consumption for the dense cloud generation stage you can use max_neighbors tweak, but it would require to start dense cloud generation again (even though the depth maps can be re-used).
Best regards,
Alexey Pasumansky,
Agisoft LLC

rexsham

  • Newbie
  • *
  • Posts: 31
    • View Profile
Re: Bad Allocation, Should I continue?
« Reply #2 on: July 04, 2019, 01:51:34 PM »
Thank you, so I can extend a lot of virtual memory using a fast SSD in order to get rid of the "bad allocation" issue right?

Alexey Pasumansky

  • Agisoft Technical Support
  • Hero Member
  • *****
  • Posts: 14099
    • View Profile
Re: Bad Allocation, Should I continue?
« Reply #3 on: July 05, 2019, 09:53:11 PM »
Hello rexsham,

In theory it is true - providing more virtual memory would solve "Bad alloc" issue.
Best regards,
Alexey Pasumansky,
Agisoft LLC