Crash to desktop while reconstructing mesh

[maddin]

I have a medium-sized project that crashes PhotoScan Pro 64bit 1.2.6 AND 1.3.0 to desktop when reconstructing the mesh from the dense point cloud.

Attached is the details page of the report in 1.2.6, using a mesh based on the low-res point cloud.

Any ideas what could be wrong?

Thanks!

[Alexey Pasumansky]

Hello maddin,

Do you have processing log for the operation or probably you have submitted the crash report?

Also what are the computer specifications and what were the mesh reconstruction settings used.

[maddin]

Do you have processing log for the operation or probably you have submitted the crash report?

I don't see any option to submit a crash report - how would that work? The crash is immediately to desktop, no warning whatsoever.

Attached is the log file I just generated right before the crash.

BTW, I also noticed it is crashing Firefox, too...!

Also what are the computer specifications and what were the mesh reconstruction settings used.

Win7 64bit SP1, 64GB RAM, GTX 1080 with 8GB VRAM, 24 core Intel Xeon E5-2687W v4 3GHz

Settings for dense mesh creation were:
Arbitray, Dense cloud, High (about 9 Mio. faces), Interpolation enabled, all point classes (I don't have any in the project)

[maddin]

Follow-up: From inspecting the Event Viewer, it looks like the system is simply running out of memory (64GB?!)...
A bit weird not to see any warning message, but maybe the project is too large?

[Alexey Pasumansky]

Hello maddin,

Usually PhotoScan displays "not enough memory" message when there's insufficient RAM to complete the operation.

Crashes and such silent program window close may be related to hardware issues (I can suggest to check RAM modules) or by some OS settings.

Note that Arbitrary mesh generation mode is very resource demanding operation.

[maddin]

It seems the "interpolation' is causing the problems? Without it, I can build a mesh at low resolution (1 Mio. faces), with it enabled, I get a crash (and an error message this time). Attached is the log.

This also works for High Resolution (9 Mio faces), but only without interpolation.

[maddin]

I can confirm that the crash is related to using Interpolation.
Attached is a screenshot of what taskmanager looks like when a crash occurs, while doing a 'low' mesh resolution but with interpolation on. Without interpolation, this works just fine (but the result is pretty bad due to many tiny holes).

[Thibaud Capra]

If holes are tiny, you can still fill holes after and that'd we a way around the issue... Though it wouldn't fix it.

[maddin]

Also to note: I can split the chunk in two and reconstruct a mesh for each independently without issues (at High detail, with interpolation on) just by reducing the bounding box size for each chunk accordingly.

Seems weird to me that such a simple procedure works and isn't built into the program.

[Alexey Pasumansky]

Hello maddin,

Do you have swap enabled in your system? It looks like the process is automatically killed when it exceeds the RAM limit.

[maddin]

Do you have swap enabled in your system? It looks like the process is automatically killed when it exceeds the RAM limit.

Now that's slightly embarrassing... - my page file was set to 500MB by the guys setting up the machine for me, and it was never changed to anything appropriate later on! I have increased the swap to 64GB, let's see whether this will help around the memory peak.

Thanks!