Graph is being computed externally

[Chris Clawson]

Crash?

Meshroom Windows 2020.1.0

Threadripper 32 core 128Gb ram

2 GPUs , NIVDIA GeForce GTX Titan Black and NVIDIA Quadro P2000

Fabian - congradulations on the long awaited release!

I am still investigating, but this this has stopped and closed Meshroom twice, for the same reason, but at different times.

I have 133 JPG images and am using both sift and akaze for Feature Extraction. This step has broken the job into 4 parts (0,1,2,3). The first time, part 1 finished (two blocks total), but then stopped and eventually closed (or crashed). When restarting and loading the same file, the Stop/Start buttons are grey, and the message "Graph is being computed externally" is displayed below the buttons.

Trying the second time, the Feature Extraction completed all 4 blocks and then stalled in the same way. The log does not report any error. I cannot start the reloaded file - the same "graph" message remains and neither Start or Stop are available.

I did earlier make a very nice mesh from another dataset of 43 JPG images, using only Sift for the Feature extraction.

Any ideas, work arounds or fixes? I will post additional info in this thread as I learn it.

Could this problem be related to the beautiful new performance graphs I have discovered in the new job tab?

[jean-marc Muroni]

Hello,

I have the same problem.

Would the new version be unstable?

[Fabien Castan]

Hi,

Thanks for the report. Could you monitor the RAM usage just before the crash? This sounds surprising with 128G of RAM.

> Any ideas, work arounds or fixes?

On the FeatureExtraction node, you can limit the max number of threads used, which will limit the RAM usage.

---

De : alice...@googlegroups.com <alice...@googlegroups.com> de la part de Chris Clawson <industr...@gmail.com>
Envoyé : dimanche 11 octobre 2020 20:17
À : AliceVision <alice...@googlegroups.com>
Objet : Graph is being computed externally

 

⚠️ Do not click or open unknown attachments ⚠️ **

--
You received this message because you are subscribed to the Google Groups "AliceVision" group.
To unsubscribe from this group and stop receiving emails from it, send an email to alicevision...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/alicevision/fa0b6cf4-09f9-4226-8fd5-518b55ff0311n%40googlegroups.com.

[Chris Clawson]

According to your new graph, my system memory usage never got higher than 30%

The same images and settings were then tried in Linux Ubuntu 20, and the program completed all the steps and finished with a textured model.

I then attempted to run a similar setup (in Windows 10), but with a smaller image set and using only Akase as my describer type. The FeatureExtraction step completed, but ImageMatching immediately failed. The log says it can't find the descriptor 12752658 in C:/(blah blah/.... The descriptor file is clearly there and may be addressed directly by using the command prompt terminal window and path copied from the log to locate the file.

[Fabien Castan]

The ImageMatching uses a vocabularyTree file. We only provide one vocabularyTree trained for SIFT.

So, you cannot use the voctree in ImageMatching using only AKAZE.

---

De : alice...@googlegroups.com <alice...@googlegroups.com> de la part de Chris Clawson <industr...@gmail.com>

Envoyé : lundi 12 octobre 2020 15:11
À : AliceVision <alice...@googlegroups.com>
Objet : Update: Graph is being computed externally

 

To view this discussion on the web visit https://groups.google.com/d/msgid/alicevision/9a50b8e2-6afa-429d-ac96-60ba4042bf6an%40googlegroups.com.

[Chris Clawson]

The Meshroom 2020.1.0 crashes when Akaze is enabled. The error usually occurs in the FeatureExtraction step. A job with a small quantity of images (like 32) seems to do okay, but larger image numbers increase the likelihood of failure. Sift alone seems to work fine.

I spent a lot of time testing the possibility that a freshly booted system may have uninitialized hardware. I would let my first try crash and then delete the cache. I would then restart my saved .mg file and things seemed to run better. My 144 image job would now finish FeatureExtraction, when it was crashing earlier. I then attempted my 2300 image job and it still would crash at some chunk in FeatureExtraction.

This morning, I have physically removed one of my GPUs (a GTX Titan Black) and rebooted, to test the system with only one GPU. The 2300 image job crashed in chunk '2' of the FeatureExtraction step. I deleted the cache and restarted Meshroom. I ran the same 2300 image job (with only the Quadro P2000 gpu in the system) and this time the program ran further and finally failed at chunk #10. For some reason, the program seems to be able to run further after deleting a failed cache and restarting.

This problem happens regardless of the 'force cpu' setting, in FeatureExtraction. A similar setup, using the 2300 image source and Akaze runs without error under Linux.

Any attempt to restart Meshroom and start the same job with a failed cache displays the message “Graph is being computed externally”. What graph? The one displayed in the Statistics window? Is that a symptom or cause of the problem? By the way, the Statistics tab will only display one GPU, even if two are in the system.

I am conducting these tests, while monitoring my system resources and do not see any resource being exhausted. I am ready to test anything I can. Please guide me in helping resolve this problem.

[Fabien Castan]

Let me know if you still have issues with 2020.1.1.

Best,