$ drmemory.exe -light -- SYCL-ray-tracing.exe
~~Dr.M~~ Dr. Memory version 2.6.0
~~Dr.M~~ Running "SYCL-ray-tracing.exe"
~~Dr.M~~ Using system call file F:\Programmes\DrMemory\drmemory\logs\symcache\syscalls_x64.txt
[1280x720]: 64 samples

~~Dr.M~~
~~Dr.M~~ Error #1: INVALID HEAP ARGUMENT to free 0x0000021580b20ec0
~~Dr.M~~ # 0 replace_free                                                 [D:\a\drmemory\drmemory\common\alloc_replace.c:2710]
~~Dr.M~~ # 1 sycl6.dll!sycl::_V1::handler::~handler                      +0x2d9    (0x00007ffc4d09d4ca <sycl6.dll+0x21d4ca>)
~~Dr.M~~ # 2 sycl6.dll!sycl::_V1::queue::ext_codeplay_supports_fusion    +0x32b    (0x00007ffc4d09cebc <sycl6.dll+0x21cebc>)
~~Dr.M~~ # 3 sycl6.dll!sycl::_V1::queue::submit_impl                     +0x4e     (0x00007ffc4d09c5ff <sycl6.dll+0x21c5ff>)
~~Dr.M~~ # 4 main                                                         [...\main.cpp:54]
~~Dr.M~~ Note: @0:00:09.798 in thread 24768
~~Dr.M~~ Note: refers to -32 byte(s) beyond last valid byte in prior malloc
~~Dr.M~~ Note: prev lower malloc:  0x0000021580b20ec0-0x0000021580b20ee0
<Application ...SYCL-ray-tracing-vs-windows\x64\Release\SYCL-ray-tracing.exe (25116).  Dr. Memory internal crash at PC 0x00000000710864e1.  Please report this at http://drmemory.org/issues along with the results of running '-debug -dr_debug'.  Program aborted.
0xc0000005 0x00000000 0x00000000710864e1 0x00000000710864e1 0x0000000000000001 0x0000000000000000
Base: 0x0000000071000000
Registers: eax=0x0000000000000075 ebx=0x000000000000001f ecx=0x0000000071120cb0 edx=0x0000000000000001
        esi=0x0000000000000000 edi=0x00000215ee8adb50 esp=0x00000215edc51b60 ebp=0x00000215edc51bf9
        r8 =0x0000000000000000 r9 =0x0000000000000000 r10=0x0000000000000002 r11=0x00000215edc51b20
        r12=0x0000000000000000 r13=0x0000000000000000 r14=0x0000000000000000 r15=0x0000000000000000
        eflags=0x0000021500010246
2.6.0-0-(Sep 21 2023 17:38:58) WinVer=105;Rel=2009;Build=22621;Edition=Core
-no_dynamic_options -disasm_mask 8 -logdir 'F:\Programmes\DrMemory\drmemory\logs\dynamorio' -client_lib 'F:\Programmes\DrMemory\bin64\release\drmemorylib.dll;0;`-light` -logdir `F:\Programmes\DrMemory\drmemory\logs` -symcache_dir `F:\Programmes\DrMemory\drmemory\logs\symcache` -lib_blocklist_default `C:\Windows*.d??,C:\P
0x00000215edc51bf9 0x0000000000000000>
~~Dr.M~~ WARNING: application exited with abnormal code 0xffffffff

//////////////////////////////////////////////////////////////////////////////////////////
//////////////////////////////////////////////////////////////////////////////////////////
//////////////////////////////////////////////////////////////////////////////////////////
Note:
The 'Error #1: INVALID HEAP ARGUMENT to free 0x0000021580b20ec0' doesn't seem to be related to the problem. It seems like it comes from the SYCL implementation.

main.cpp:54 is this line:
queue.submit([&](sycl::handler& handler) {

When commenting the call to parallel_for() (main.cpp:67):
handler.parallel_for(coordinates_indices, render_kernel);

The Error #1 is gone.

But, when replacing
handler.parallel_for(coordinates_indices, render_kernel);

by

handler.parallel_for(coordinates_indices, [](const sycl::nd_item<2>& coordinates) {
    });

which is an empty  kernel call, the Error #1 is back. So this is why I assume
that Error #1 is unrelated to the problem because it's there even when none on my
kernel code is executed.