Illegal CUDA Address Error

[sepigraph]

Regardless of whatever images I input, with Metashape 2.2.1 Standard, every time during matching pairs I get an illegal CUDA address accessed encountered and the software locks up and my GPU crashes, causing me to hard-shutoff and reboot my workstation. I've checked %APPDATA% and there is no crash log. The error in the progress log during matching looks something like:

Error: cudaFree(data_): an illegal memory access was encountered (700) at line 132
Warning: cudaStreamDestroy failed: an illegal memory access was encountered (700)

I have an NVidia 5070ti and 64GB RAM. I've updated the driver to 576.xx which made no difference (even ran into a black screen issue, so had to roll driver back to 572.40).

[Alexey Pasumansky]

Hello sepigraph,

Please send the complete log corresponding to the failed operation to support@agisoft.com.

Enable Write log to file option in the general preferences tab, specify the path to file to be created, then re-start Metashape and try to reproduce the issue, when it occurs, send the saved log to us.

[sepigraph]

Here is the process log attached.

[Alexey Pasumansky]

Hello sepigraph,

Does it help to save the project in PSX format before the processing?

Also please check, if the matching can be completed when Guided matching is disabled.

[indesinenter]

Hello sepigraph,

Does it help to save the project in PSX format before the processing?

Also please check, if the matching can be completed when Guided matching is disabled.

Hi Alexey,

I also had this problem (Ubuntu, 5080Ti, Driver 570)  and have been following this thread/forum. When I ran the process without Guided Matching, the CUDA errors disappeared.

Do you know, or can you estimate, what performance difference there is between using CUDA and OpenCL?

Thanks in advance.

[Alexey Pasumansky]

Hello indesinenter,

Can you share the log related to the failed matching operation with Guided Matching option enabled?
Please also specify Metashape version used and NVIDIA driver version installed.

Also you can try to switch to OpenCL implementation and check, if it works on the same configuration with the guided matching enabled.

The processing performance difference between CUDA and OpenCL implementation should be minimal and may depend on OS, driver, GPU model, etc. But in most cases it can be neglected.

[Alexey Pasumansky]

Everyone who has issues with Guided Image Matching run on NVIDIA GeForce RTX 50 series, please check version 2.2.2 pre-release:
https://download.agisoft.com/metashape-pro_2_2_2_x64.msi
https://download.agisoft.com/metashape-pro_2_2_2_amd64.tar.gz

[Eric Gilson]

This problem occurred to me as well this week. I will try the new pre release and see if that helps.

The first attempt with a folder that had given me problems seemed to work. Too bad i bought a new card today (5080) thinking something was wrong with the last one (5070TI)...Guess my son is getting an updated card at a the friends and family discount...

[Alexey Pasumansky]

Hello Eric,

I think the reported problem should be fixed for you in 2.2.2.

In case you face a freezing issue during the depth maps generation similar to the one reported in that thread: https://www.agisoft.com/forum/index.php?topic=17307.15
Try the suggested tweak for max_multipier, while we are trying to fix the problem on Metashape side.