intel / intel/llvm

scheduler/./SchedulerTests.exe/9/12 DependsOnTests.EnqueueNoMemObjTwoHostTasks failing on Windows on unrelated changes

Open
#14,060 0 comments 0 reactions 0 assignees View on GitHub
bug confirmed
Dominant language
LLVM
Stars
1.5k
Forks
854
Avg merge
3d 17h
Merged PRs (30d)
137

Description

### Describe the bug

https://github.com/intel/llvm/actions/runs/9388806833/job/25854848527

```
[ RUN ] DependsOnTests.EnqueueNoMemObjTwoHostTasks

Exception Code: 0xC0000005

#0 0x00007ff6923d2333 sycl::_V1::detail::plugin::call_nocheck<35, struct _pi_mem *>(struct _pi_mem *) const D:\github\_work\llvm\llvm\src\sycl\source\detail\plugin.hpp:271:0

#1 0x00007ff6923fe24a sycl::_V1::detail::plugin::call D:\github\_work\llvm\llvm\src\sycl\source\detail\plugin.hpp:297:0

#2 0x00007ff6923fe24a sycl::_V1::detail::memReleaseHelper D:\github\_work\llvm\llvm\src\sycl\source\detail\memory_manager.cpp:194:0

#3 0x00007ff6923fe24a sycl::_V1::detail::MemoryManager::releaseMemObj(class std::shared_ptr, class sycl::_V1::detail::SYCLMemObjI *, void *, void *) D:\github\_work\llvm\llvm\src\sycl\source\detail\memory_manager.cpp:275:0

#4 0x00007ff6924b2b56 sycl::_V1::detail::SYCLMemObjT::releaseMem(class std::shared_ptr, void *) D:\github\_work\llvm\llvm\src\sycl\source\detail\sycl_mem_obj_t.cpp:127:0

#5 0x00007ff6923fe08d sycl::_V1::detail::MemoryManager::release(class std::shared_ptr, class sycl::_V1::detail::SYCLMemObjI *, void *, class std::vector, class std::allocator>>, struct _pi_event *&) D:\github\_work\llvm\llvm\src\sycl\source\detail\memory_manager.cpp:258:0

#6 0x00007ff69248caac sycl::_V1::detail::ReleaseCommand::enqueueImp(void) D:\github\_work\llvm\llvm\src\sycl\source\detail\scheduler\commands.cpp:1279:0

#7 0x00007ff69248a5c1 sycl::_V1::detail::Command::enqueue(struct sycl::_V1::detail::EnqueueResultT &, enum sycl::_V1::detail::BlockingT, class std::vector> &) D:\github\_work\llvm\llvm\src\sycl\source\detail\scheduler\commands.cpp:884:0

#8 0x00007ff6924a28b2 sycl::_V1::detail::Scheduler::GraphProcessor::enqueueCommand(class sycl::_V1::detail::Command *, class std::shared_lock &, struct sycl::_V1::detail::EnqueueResultT &, class std::vector> &, class sycl::_V1::detail::Command *, enum sycl::_V1::detail::BlockingT) D:\github\_work\llvm\llvm\src\sycl\source\detail\scheduler\graph_processor.cpp:145:0

#9 0x00007ff6924a2476 sycl::_V1::detail::Scheduler::waitForRecordToFinish(struct sycl::_V1::detail::MemObjRecord *, class std::shared_lock &) D:\github\_work\llvm\llvm\src\sycl\source\detail\scheduler\scheduler.cpp:82:0

#10 0x00007ff6924a18f3 sycl::_V1::detail::Scheduler::removeMemoryObject(class sycl::_V1::detail::SYCLMemObjI *, bool) D:\github\_work\llvm\llvm\src\sycl\source\detail\scheduler\scheduler.cpp:293:0

#11 0x00007ff6924a087e sycl::_V1::detail::Scheduler::cleanupDeferredMemObjects(enum sycl::_V1::detail::BlockingT) D:\github\_work\llvm\llvm\src\sycl\source\detail\scheduler\scheduler.cpp:552:0

#12 0x00007ff6924a02a3 sycl::_V1::detail::Scheduler::cleanupCommands(class std::vector> const &) D:\github\_work\llvm\llvm\src\sycl\source\detail\scheduler\scheduler.cpp:436:0

#13 0x00007ff69249d86c sycl::_V1::detail::Scheduler::NotifyHostTaskCompletion(class sycl::_V1::detail::Command *) D:\github\_work\llvm\llvm\src\sycl\source\detail\scheduler\scheduler.cpp:501:0

#14 0x00007ff6924803a0 sycl::_V1::detail::DispatchHostTask::operator()(void) const D:\github\_work\llvm\llvm\src\sycl\source\detail\scheduler\commands.cpp:443:0

#15 0x00007ff69239fa86 sycl::_V1::detail::ThreadPool::worker(void) D:\github\_work\llvm\llvm\src\sycl\source\detail\thread_pool.hpp:51:0

#16 0x00007ff69239b911 std::thread::_Invoke>, 0>(void *) C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\include\thread:56:0

#17 0x00007ff9e3a86b4c (C:\WINDOWS\System32\ucrtbase.dll+0x26b4c)

#18 0x00007ff9e4ba4cb0 (C:\WINDOWS\System32\KERNEL32.DLL+0x14cb0)

#19 0x00007ff9e5d3e8ab (C:\WINDOWS\SYSTEM32\ntdll.dll+0x7e8ab)

--
exit: 3221225477
```

### To reproduce

_No response_

### Environment

_No response_

### Additional context

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.