How to avoid approx2! from crashing because of Device ran out memory?

[3togo]

Due to unknown reason, approx2 will crash with the following error msg.

thread 'main' panicked at 'Error message: System or Device ran out of memory
Last error: In function virtual void* cuda::Allocator::nativeAlloc(size_t)
In file src/backend/cuda/memory.cpp:157
CUDA Error (2): out of memory

But the gpu memory usage is not very high instead.

My question is that is it possible to ignore this error and continue running the rest of the program?

[3togo]

It is something related to the Contiguous Memory Allocation. Using approx2_2 could solve that problem.
However, moddims does not have moddims_v2, the problem remains.

[3togo]

Below is the stack backtrace

thread 'main' panicked at 'Error message: System or Device ran out of memory
Last error: In function virtual void* cuda::Allocator::nativeAlloc(size_t)
In file src/backend/cuda/memory.cpp:157
CUDA Error (2): out of memory

 0# 0x00007FFF2CDAAF81 in /opt/arrayfire/lib/libafcuda.so.3
 1# 0x00007FFF2D5FF31C in /opt/arrayfire/lib/libafcuda.so.3
 2# 0x00007FFF2DA41C7B in /opt/arrayfire/lib/libafcuda.so.3
 3# 0x00007FFF2CDACFAE in /opt/arrayfire/lib/libafcuda.so.3
 4# 0x00007FFF2C7419A2 in /opt/arrayfire/lib/libafcuda.so.3
 5# 0x00007FFF2C741B04 in /opt/arrayfire/lib/libafcuda.so.3
 6# 0x00007FFF2DAA721B in /opt/arrayfire/lib/libafcuda.so.3
 7# 0x00007FFF2DAA4E19 in /opt/arrayfire/lib/libafcuda.so.3
 8# 0x00007FFF2D606D19 in /opt/arrayfire/lib/libafcuda.so.3
 9# af_moddims in /opt/arrayfire/lib/libafcuda.so.3
10# af_moddims in /opt/arrayfire/lib/libaf.so.3
11# 0x000055555556C09B in /work/gitee/j_viewr/jviewr/target/debug/jviewr
12# 0x0000555555565F0D in /work/gitee/j_viewr/jviewr/target/debug/jviewr
13# 0x0000555555566C0E in /work/gitee/j_viewr/jviewr/target/debug/jviewr
14# 0x0000555555595865 in /work', /home/eli/.cargo/registry/src/mirrors.ustc.edu.cn-12df342d903acd47/arrayfire-3.8.0/src/core/error.rs:37:14
stack backtrace:
   0: rust_begin_unwind
             at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
             at /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/core/src/panicking.rs:142:14
   2: arrayfire::core::error::handle_error_general
             at /home/eli/.cargo/registry/src/mirrors.ustc.edu.cn-12df342d903acd47/arrayfire-3.8.0/src/core/error.rs:37:14
   3: arrayfire::core::error::Callback::call
             at /home/eli/.cargo/registry/src/mirrors.ustc.edu.cn-12df342d903acd47/arrayfire-3.8.0/src/core/error.rs:29:9
   4: arrayfire::core::error::HANDLE_ERROR
             at /home/eli/.cargo/registry/src/mirrors.ustc.edu.cn-12df342d903acd47/arrayfire-3.8.0/src/core/error.rs:95:5
   5: arrayfire::core::data::moddims
             at /home/eli/.cargo/registry/src/mirrors.ustc.edu.cn-12df342d903acd47/arrayfire-3.8.0/src/core/data.rs:690:9
   6: jviewr::jviewr::screen::<impl jviewr::j_libs::j_tv::Screen>::get_depth_yxd_d_from_eyeline_depth
             at /home/eli/Desktop/jviewr/src/jviewr/screen.rs:109:9
   7: jviewr::jviewr::screen::<impl jviewr::j_libs::j_tv::Screen>::get_proj_idx_yx_i

[9prady9]

Can you please share a standalone example that can reproduce this issue.