No, the same error on Intel platform:
Windows 10 Pro x64
Processor usage: 100%
“Processing node went offline. This could be due to insufficient memory or a network error.”
Not resized images: getting error on feature search after 12 minutes running time.
Resized images: after 18 minutes.
Processing node, actually, running after error message: processor usage keeps on 100% level.
Tried to wait till processor calmed down, then restart the task: task finishes with some results. The results are not comparable with the results from Docker based WebODM with identical tasks options: the point clouds are not dense enough to create good 3D model. Same task setting makes almost perfect results on the same computer with Docker-based WebODM.
We’re still investigating. No luck for now. It seems that the process is somehow “blocking” (hang? freeze?) the computer for more than 5 minutes in the initial steps of processing. When that happens, WebODM assumes the node went offline because it hasn’t been able to communicate with for it more than 5 minutes, so it errors out. But it’s strange. Do you notice any “hanging” of the computer window or resources when you first start processing?
The fact that it seems to run fine on my machine (and plenty of other machines) makes this difficult to track and fix.
I’ve made some changes to the offline check; in a few hours, try to update by going to Tools → Check for Updates. Build 19 should address this. Please report back if the problem persists even after the update?