WebODM crashes when processing tweaked profiles

wawi

Hi!
I've been a user of WebODM for some time already, but since it became a separate tool, I love it even more – thanks, @pierotofy !

Over the last few weeks, I've done lots of testing and, regardless of the release, one bug – I believe – still pops up.
When I use out‑of‑the‑box processing profiles, everything is fine, but when I tweak pc-quality to high or ultra, WebODM always crashes on the step shown in the screenshot. The process stalls and can hang for hours. But here comes the interesting part: if I close the app and start it again, the process is finished – the task is completed with all deliverables already connected to the app (although no data is visible earlier in the storage folders), and the processing time shows 11–30+ minutes, depending on cloud density.
I've tested it on almost all profiles, and it works the same way – even in Field and Fast Ortho.

I'd appreciate any ideas on what I might be doing wrong.

My setup: AMD Ryzen 9 9950X, 128GB RAM + 14GB GPU

3 Replies

pierotofy

Mm, strange. I'm not really sure why it would hang like that. Perhaps this has happened to other people and they can chime in on it

wawi OP

Hmm, hoped someone already had similar problem.
Do users report any problem with processing when using AMD chips instead od Intels?

Airwolf

Are you able to share example console logs for both cases?

Need more help?

This discussion happened in the WebODM community Discord. Join and ask your own question.

Join View Original Thread

This page mirrors a public discussion from the WebODM Discord. How to request a removal.