Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get error when upgrade taichi from v1.0.0 to v1.0.1 #4891

Closed
beiyuouo opened this issue Apr 29, 2022 · 3 comments · Fixed by #4893
Closed

Get error when upgrade taichi from v1.0.0 to v1.0.1 #4891

beiyuouo opened this issue Apr 29, 2022 · 3 comments · Fixed by #4893
Assignees
Labels
potential bug Something that looks like a bug but not yet confirmed

Comments

@beiyuouo
Copy link

Describe the bug
Get error when upgrade taichi from v1.0.0 to v1.0.1

To Reproduce

import taichi as ti

arch = ti.vulkan if ti._lib.core.with_vulkan() else ti.cuda
ti.init(arch=arch)

Log/Screenshots
Work fine with taichi v1.0.0

python main.py
[Taichi] version 1.0.0, llvm 10.0.0, commit 6a15da85, win, python 3.8.12
[Taichi] Starting on arch=vulkan
[I 04/29/22 23:07:58.805 21276] [D:/a/taichi/taichi/taichi/backends/vulkan/vulkan_device_creator.cpp:pick_physical_device@356] Found Vulkan 
Device 0 (Intel(R) UHD Graphics 630)
[I 04/29/22 23:07:58.806 21276] [D:/a/taichi/taichi/taichi/backends/vulkan/vulkan_device_creator.cpp:pick_physical_device@356] Found Vulkan 
Device 1 (NVIDIA GeForce GTX 1660 Ti)
[I 04/29/22 23:07:58.806 21276] [D:/a/taichi/taichi/taichi/backends/vulkan/vulkan_device_creator.cpp:pick_physical_device@356] Found Vulkan 
Device 2 (Intel(R) UHD Graphics 630)
[I 04/29/22 23:07:58.806 21276] [D:/a/taichi/taichi/taichi/backends/vulkan/vulkan_device_creator.cpp:create_logical_device@424] Vulkan Device "Intel(R) UHD Graphics 630" supports Vulkan 0 version 1.2.184

Crashed when upgrade

python main.py
[Taichi] version 1.0.1, llvm 10.0.0, commit 1c3619d9, win, python 3.8.12
[Taichi] Starting on arch=vulkan
[I 04/29/22 23:10:20.113 29644] [D:/a/taichi/taichi/taichi/backends/vulkan/vulkan_device_creator.cpp:pick_physical_device@363] Found Vulkan 
Device 0 (Intel(R) UHD Graphics 630)
[I 04/29/22 23:10:20.114 29644] [D:/a/taichi/taichi/taichi/backends/vulkan/vulkan_device_creator.cpp:pick_physical_device@363] Found Vulkan 
Device 1 (NVIDIA GeForce GTX 1660 Ti)
[I 04/29/22 23:10:20.114 29644] [D:/a/taichi/taichi/taichi/backends/vulkan/vulkan_device_creator.cpp:pick_physical_device@363] Found Vulkan 
Device 2 (Intel(R) UHD Graphics 630)
[I 04/29/22 23:10:20.115 29644] [D:/a/taichi/taichi/taichi/backends/vulkan/vulkan_device_creator.cpp:create_logical_device@431] Vulkan Device "NVIDIA GeForce GTX 1660 Ti" supports Vulkan 0 version 1.3.194
Assertion failed: m_VulkanFunctions.vkGetDeviceBufferMemoryRequirements != nullptr, file D:/a/taichi/taichi/external/VulkanMemoryAllocator/include\vk_mem_alloc.h, line 14440

Additional comments
It may happen when upgrade Vulkan SDK version from 1.2.x to 1.3.x
Related issus in VulkanMemoryAllocator: #247 #256

@beiyuouo beiyuouo added the potential bug Something that looks like a bug but not yet confirmed label Apr 29, 2022
@lucifer1004
Copy link
Contributor

lucifer1004 commented Apr 30, 2022

I also encountered this issue.

[Taichi] version 1.0.1, llvm 10.0.0, commit 1c3619d9, linux, python 3.9.12
[Taichi] Starting on arch=vulkan
[I 04/30/22 08:38:43.716 587702] [vulkan_device_creator.cpp:pick_physical_device@363] Found Vulkan Device 0 (NVIDIA TITAN RTX)
[I 04/30/22 08:38:43.716 587702] [vulkan_device_creator.cpp:pick_physical_device@363] Found Vulkan Device 1 (llvmpipe (LLVM 12.0.0, 256 bits))
[I 04/30/22 08:38:43.736 587702] [vulkan_device_creator.cpp:create_logical_device@431] Vulkan Device "NVIDIA TITAN RTX" supports Vulkan 0 version 1.3.194
python3: /home/dev/taichi/external/VulkanMemoryAllocator/include/vk_mem_alloc.h:14440: void VmaAllocator_T::ValidateVulkanFunctions(): Assertion `m_VulkanFunctions.vkGetDeviceBufferMemoryRequirements != nullptr' failed.

@STRRL
Copy link

STRRL commented Apr 30, 2022

+1

The bypass solution is pining the taichi version to 1.0.0

@bobcao3 bobcao3 self-assigned this Apr 30, 2022
@bobcao3
Copy link
Collaborator

bobcao3 commented Apr 30, 2022

Somehow this issue cropped up again... Might be that we recently updated Vulkan Memory Allocator and did not add this function pointer in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
potential bug Something that looks like a bug but not yet confirmed
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants