Agisoft Metashape

Agisoft Metashape => Bug Reports => Topic started by: wojtek on May 13, 2020, 11:53:58 AM

Title: Lack of disk space during depth based meshing == hard crash
Post by: wojtek on May 13, 2020, 11:53:58 AM
When Metashape runs out of disk space during depth map based mesh reconstruction it will crash without any sort of warning or crash report.

I think ideally it should pause when disk space runs low, instead?

Title: Re: Lack of disk space during depth based meshing == hard crash
Post by: Alexey Pasumansky on May 13, 2020, 11:57:02 AM
Hello wojtek,

Which OS you are using?
Title: Re: Lack of disk space during depth based meshing == hard crash
Post by: wojtek on May 13, 2020, 12:10:46 PM
Windows 10 currently but I think I had this happen on 7 before, too.
Title: Re: Lack of disk space during depth based meshing == hard crash
Post by: wojtek on June 09, 2021, 09:40:12 AM
This is still an issue in 1.7.2.


Guys, can't you just pause the process when the disk space is low?
Title: Re: Lack of disk space during depth based meshing == hard crash
Post by: Vladimir Denisov on June 10, 2021, 11:43:28 AM
This is still an issue in 1.7.2.


Guys, can't you just pause the process when the disk space is low?


How many disk space you have?
Have you another disk?
How many photos in project's chunk?

In my project now 20000 photos. We use M.2 SSD 500Gb disk as project's storage. How I solve problem with free space? i use region to make model's part, and when I need to make another part - I just make offset region position to half size in any axis (by script).
Title: Re: Lack of disk space during depth based meshing == hard crash
Post by: wojtek on June 13, 2021, 03:47:04 PM
This is still an issue in 1.7.2.


Guys, can't you just pause the process when the disk space is low?


How many disk space you have?
Have you another disk?
How many photos in project's chunk?

In my project now 20000 photos. We use M.2 SSD 500Gb disk as project's storage. How I solve problem with free space? i use region to make model's part, and when I need to make another part - I just make offset region position to half size in any axis (by script).

I don't think any of the above really matters. Regardless of specs, It's just really impractical how it works now. Checking remaining disk space periodically shouldn't be difficult to implement. Model generation temp files add up really quickly and are not recoverable if the app crashes.