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

memory sanitizer reports errors for simple example #298

Closed
mkandulavm opened this issue Aug 11, 2022 · 4 comments
Closed

memory sanitizer reports errors for simple example #298

mkandulavm opened this issue Aug 11, 2022 · 4 comments

Comments

@mkandulavm
Copy link

mkandulavm commented Aug 11, 2022

Hi

I am trying to integrate the given simple multiplication example into a project. I use the memory sanitizer by default and it is showing following info.

single_include/kompute/Kompute.hpp:1049:30: runtime error: member call on address 0x555559947500 which does not point to an object of type 'TensorT'
0x555559947500: note: object has invalid vptr

Please help on how to proceed.

Also, in debug mode I am getting a segmentation fault in manager.cpp at this line
this->mInstance->destroyDebugReportCallbackEXT(

why is this happening ?

@mkandulavm
Copy link
Author

Once I defined this , the problem got resolved
KOMPUTE_OPT_DISABLE_VK_DEBUG_LAYERS

thank you.

@axsaucedo
Copy link
Member

Nice - thank you for updating, it does seem like there is a raised warning from the debug layers so we'll have a look. Thank you for reporting

@feliwir
Copy link

feliwir commented Jun 28, 2023

I'm getting a crash for this line aswell:

[Jun 28 2023 13:36:45] [debug] [/home/stephan/Development/bcenc-gpu/build/_deps/kompute-src/src/Manager.cpp:26] [VALIDATION]: Validation - Validation Error: [ UNASSIGNED-Threading-Info ] Object 0: handle = 0x12460c0, type = VK_OBJECT_TYPE_DEBUG_REPORT_CALLBACK_EXT; | MessageID = 0x5d6b67e2 | Couldn't find VkDebugReportCallbackEXT Object 0x12460c0. This should not happen and may indicate a bug in the application.

@axsaucedo
Copy link
Member

@feliwir thank you for reporting this issue, however it seems it's a different issue, quite a strange one.

Could you please create a new issue with the details on your versions of vulkan, etc (as per the issue creation tempalte)?

We'll close this issue as several debug layer issues have been resolved since the most recent version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants