Ubsan invalid vptr errors in TBB #99385

New Issue

Martijn Versteegh · 2022-07-04T11:19:59+02:00

Martijn Versteegh commented

2022-07-04 11:19:59 +02:00

System Information
Operating system: Linux-5.4.0-121-generic-x86_64-with-glibc2.31 64 Bits
Graphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.129.06

Blender Version
Broken: version: 3.2.0, branch: Unknown, commit date: Unknown Unknown, hash: rBUnknown *3.3 aplha still broken as of today
Worked:

Short description of error
When loading a .blend file with a node group containing a RayCast node in a developer-debug build the following error message is shown in the console :

/home/martijn/progs/blender-git/lib/linux_centos7_x86_64/tbb/include/tbb/task.h:870:9: runtime error: member call on address 0x613000160740 which does not point to an object of type 'task'
0x6130001706c0: note: object has invalid vptr
 00 00 00 00  be be be be be be be be  be be be be be be be be  be be be be be be be be  be be be be
              ^~~~~~~~~~~~~~~~~~~~~~~
              invalid vptr

Exact steps for others to reproduce the error

Compile blender with 'developer debug' options.
Open the attached blend file.
Look in the console.

test.blend

**System Information** Operating system: Linux-5.4.0-121-generic-x86_64-with-glibc2.31 64 Bits Graphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.129.06 **Blender Version** Broken: version: 3.2.0, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown` *3.3 aplha still broken as of today Worked: **Short description of error** When loading a .blend file with a node group containing a RayCast node in a developer-debug build the following error message is shown in the console : ``` /home/martijn/progs/blender-git/lib/linux_centos7_x86_64/tbb/include/tbb/task.h:870:9: runtime error: member call on address 0x613000160740 which does not point to an object of type 'task' 0x6130001706c0: note: object has invalid vptr 00 00 00 00 be be be be be be be be be be be be be be be be be be be be be be be be be be be be ^~~~~~~~~~~~~~~~~~~~~~~ invalid vptr ``` **Exact steps for others to reproduce the error** - Compile blender with 'developer debug' options. - Open the attached blend file. - Look in the console. [test.blend](https://archive.blender.org/developer/F13257147/test.blend)

Martijn Versteegh commented

2022-07-04 11:19:59 +02:00

Added subscriber: @Baardaap

Jacques Lucke commented

2022-07-04 15:30:45 +02:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2022-07-04 15:30:45 +02:00

Think I've seen that before and we classified that as a bug in tbb, couldn't find the task where we talked about this before unfortunately.

Richard Antalik commented

2022-07-04 20:12:32 +02:00

Added subscriber: @iss

Richard Antalik commented

2022-07-04 20:12:32 +02:00

Can't reproduce here (Windows build). Also can't find duplicate task.

Martijn Versteegh commented

2022-07-04 22:55:04 +02:00

I'll see if I can test on another linux with another TBB version...

Martijn Versteegh commented

2022-07-05 11:39:23 +02:00

This comment was removed by @Baardaap

*This comment was removed by @Baardaap*

Germano Cavalcante commented

2022-07-05 20:45:38 +02:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2022-07-05 20:45:38 +02:00

Tested with Windows + ASAN. No error message.

Must be something seen only on Linux.

Tested with Windows + ASAN. No error message. Must be something seen only on Linux.

Ray molenkamp commented

2022-07-05 21:19:42 +02:00

Added subscribers: @ideasman42, @LazyDodo

Ray molenkamp commented

2022-07-05 21:19:42 +02:00

The error shown is a ubsan one not asan (so you'll never see it with MSVC), I was convinced we do not take issues like that on the tracker as they are usually just "noise", nice to have more correct code, but wasteful on resources, as there's about a 1000 actual bugs to look at, but @ideasman42 recently gave the OK for #99382 so my knowledge about that is likely outdated.

Martijn Versteegh commented

2022-07-05 23:15:34 +02:00

I don't really care either way. It looked scary, like TBB complained of getting random pointers to execute as function pointers. But if it's just something on my system, or just a false positive from somewhere it's fine with me to close this and move on.

The only disadvantage is that someone else will probably report it sooner or later. Because if you don't really know what the error/warning means (like me) it looks mighty scary.

edit: I saw I didn't paste in the complete error message. Oops. Added it in case it changes anything (probably not).

I don't really care either way. It looked scary, like TBB complained of getting random pointers to execute as function pointers. But if it's just something on my system, or just a false positive from somewhere it's fine with me to close this and move on. The only disadvantage is that someone else will probably report it sooner or later. Because if you don't really know what the error/warning means (like me) it looks mighty scary. edit: I saw I didn't paste in the complete error message. Oops. Added it in case it changes anything (probably not).

Philipp Oeser commented

2022-08-19 12:14:56 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2022-08-19 12:14:56 +02:00

make debug developer gives me this in current master (ab3e9c47d8):

/linux_centos7_x86_64/usd/lib/libusd_usd_m.a(mallocHook.cpp.o):mallocHook.cpp:function usdBlender__pxrReserved__::ArchMallocHook::Initialize(void* (*)(unsigned long, void const*), void* (*)(void*, unsigned long, void const*), void* (*)(unsigned long, unsigned long, void const*), void (*)(void*, void const*), std::string*): error: undefined reference to '__malloc_hook'
collect2: error: ld returned 1 exit status
make[3]: *** [source/creator/CMakeFiles/blender.dir/build.make:564: bin/blender] Error 1
make[2]: *** [CMakeFiles/Makefile2:9566: source/creator/CMakeFiles/blender.dir/all] Error 2

`make debug developer` gives me this in current master (ab3e9c47d8): ``` /linux_centos7_x86_64/usd/lib/libusd_usd_m.a(mallocHook.cpp.o):mallocHook.cpp:function usdBlender__pxrReserved__::ArchMallocHook::Initialize(void* (*)(unsigned long, void const*), void* (*)(void*, unsigned long, void const*), void* (*)(unsigned long, unsigned long, void const*), void (*)(void*, void const*), std::string*): error: undefined reference to '__malloc_hook' collect2: error: ld returned 1 exit status make[3]: *** [source/creator/CMakeFiles/blender.dir/build.make:564: bin/blender] Error 1 make[2]: *** [CMakeFiles/Makefile2:9566: source/creator/CMakeFiles/blender.dir/all] Error 2 ```

Brecht Van Lommel commented

2022-08-19 14:41:01 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2022-08-19 14:41:01 +02:00

@lichtwerk, possibly related to this, though not sure why it would happen only with asan:
https://devtalk.blender.org/t/building-blender-on-linux-using-glibc-2-34-raises-linking-errors-from-the-usd-library/24185

@lichtwerk, possibly related to this, though not sure why it would happen only with asan: https://devtalk.blender.org/t/building-blender-on-linux-using-glibc-2-34-raises-linking-errors-from-the-usd-library/24185

Brecht Van Lommel changed title from ~~Raycast Node causes TBB error message in 'developer debug' build.~~ to Ubsan invalid vptr errors in TBB

2022-08-19 14:43:11 +02:00

Brecht Van Lommel commented

2022-08-19 14:43:11 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Ray molenkamp commented

2022-08-19 14:46:22 +02:00

@brecht it's the "debug" that triggers this rather than the asan, USD 22.08 has a fix, but the IO team chose to stay on 22.03 so best way to sidestep this for now is to build WITH_USD off in debug builds with new glibc

@brecht it's the "debug" that triggers this rather than the asan, USD 22.08 has a fix, but the IO team chose to stay on 22.03 so best way to sidestep this for now is to build `WITH_USD` off in debug builds with new glibc

Brecht Van Lommel commented

2022-08-19 14:46:57 +02:00

I think it's generally fine to keep track of these as todo issues, just not as bugs.

Brecht Van Lommel commented

2022-08-19 15:07:41 +02:00

In #99385#1406106, @LazyDodo wrote:
@brecht it's the "debug" that triggers this rather than the asan, USD 22.08 has a fix, but the IO team chose to stay on 22.03 so best way to sidestep this for now is to build WITH_USD off in debug builds with new glibc

Ok, if it's a serious problem for developers they could look into adding the symbols to libc_compat (also in LTS branches).

> In #99385#1406106, @LazyDodo wrote: > @brecht it's the "debug" that triggers this rather than the asan, USD 22.08 has a fix, but the IO team chose to stay on 22.03 so best way to sidestep this for now is to build `WITH_USD` off in debug builds with new glibc Ok, if it's a serious problem for developers they could look into adding the symbols to libc_compat (also in LTS branches).

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Ubsan invalid vptr errors in TBB #99385