Forums Technical Discussion [SOLVED] Consistent crash on Ubuntu 22.04

[SOLVED] Consistent crash on Ubuntu 22.04

   4696   13   3
User Avatar
monomon
Member
40 posts
Joined: May 2019
Offline
 
I installed 19.5.435 on Ubuntu 22.04, but it is crashing constantly.
I ran `source houdini_setup_bash`, added also `/lib/x86_64-linux-gnu` to LD_LIBRARY_PATH (since I needed this on another Ubuntu machine). But none of this helped. Any ideas? It seems to segfault quite early in the process.

Crash report from bottleship; Houdini Core Version 19.5.435 [linux-x86_64-gcc9.3]
Uptime 1 seconds
Wed Feb  1 16:19:28 2023
Caught signal 11

Traceback from 1182530 ThreadId=0x7fd695823e80
AP_Interface::coreDumpChaser(UTsignalHandlerArg) <libHoudiniUI.so>
AP_Interface::si_CrashHandler::chaser(UTsignalHandlerArg) <libHoudiniUI.so>
signalCallback(UTsignalHandlerArg) <libHoudiniUT.so>
UT_Signal::UT_ComboSignalHandler::operator()(int, siginfo_t*, void*) const <libHoudiniUT.so>
UT_Signal::processSignal(int, siginfo_t*, void*) <libHoudiniUT.so>
__sigaction <libc.so.6>
Edited by monomon - Feb. 3, 2023 06:22:23
 Report
User Avatar
johnmather
Staff
528 posts
Joined: Aug. 2019
Offline
 
Unfortunately that stack trace doesn't provide any information on what exactly went wrong. Have you tried without setting LD_LIBRARY_PATH?
 Report
User Avatar
monomon
Member
40 posts
Joined: May 2019
Offline
 
Thanks for the response, yes I tried all kinds of permutations of sourcing the setup script, setting env vars and not.
I realize this stack is very short and shows almost nothing. Could it be caused by missing libraries? Any way to validate this?
 Report
User Avatar
johnmather
Staff
528 posts
Joined: Aug. 2019
Offline
 
You could try this.

source houdini_setup
sudo apt install gdb
gdb houdini

Then, in gdb, once you get the (gdb)prompt, type run.

Once it crashes, type: thread apply all bt
Copy and paste all of the output from when you started gdb to the output of the previous command and attach it here. Hopefully it will give us a clue.
 Report
User Avatar
monomon
Member
40 posts
Joined: May 2019
Offline
 
Weird, there is almost nothing in this trace. Could it be that the installed video drivers are not the right ones?

Starting program: /opt/hfs19.5.435/bin/houdinicore-bin 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Detaching after fork from child process 2240132]
[Inferior 1 (process 2240076) exited normally]
(gdb) No OpenCL platform has the specified device type (HOUDINI_OCL_DEVICETYPE): GPU.
  Falling back to built-in CPU OpenCL driver (see HOUDINI_USE_HFS_OCL)
No OpenCL platform has the specified device type (HOUDINI_OCL_DEVICETYPE): GPU.
  Falling back to built-in CPU OpenCL driver (see HOUDINI_USE_HFS_OCL)
2240132: Fatal error: Segmentation fault (sent by pid 0)
Crash log saved to /tmp/houdini_temp/crash.untitled.bottleship_2240132_log.txt
thread apply all bt
 Report
User Avatar
monomon
Member
40 posts
Joined: May 2019
Offline
 
Changed the library path a bit

source houdini_setup_bash
LD_LIBRARY_PATH="/lib/x86_64-linux-gnu:/opt/hfs19.5/dsolib:/opt/hfs19.5/python/lib" LD_PRELOAD="/lib/x86_64-linux-gnu/libc_malloc_debug.so.0" /opt/hfs19.5/bin/houdinicore

And now I am getting
/opt/hfs19.5/bin/houdinicore-bin: symbol lookup error: /opt/hfs19.5/dsolib/libHoudiniUI.so: undefined symbol: _ZnwmSt11align_val_t, version Qt_5

Is this related to the gcc version that libQt* were compiled with?
 Report
User Avatar
monomon
Member
40 posts
Joined: May 2019
Offline
 
Here is ldd /opt/hfs19.5/dsolib/libHoudiniUI.so

Edit: btw I also tried removing the Qt libraries and using the system ones, but then I get other missing symbols.
Edited by monomon - Feb. 3, 2023 04:02:22

Attachments:
houdini-ui-ldd (9.7 KB)

 Report
User Avatar
monomon
Member
40 posts
Joined: May 2019
Offline
 
Turned out the nvidia driver was not being used. After configuring it, it worked.
 Report
User Avatar
johnmather
Staff
528 posts
Joined: Aug. 2019
Offline
 
I'm glad you figured it out. fyi, adding /lib/x86_64-linux-gnu/libc_malloc_debug.so.0 to your LD_PRELOAD is no longer needed as of 19.0.594 and will greatly reduce performance.
 Report
User Avatar
monomon
Member
40 posts
Joined: May 2019
Offline
 
Oh cool thanks. Is a vendored libc being used?
 Report
User Avatar
johnmather
Staff
528 posts
Joined: Aug. 2019
Offline
 
No, we fixed the underlying compatibility issue with glibc 2.34+.
 Report
User Avatar
rmon61
Member
7 posts
Joined: March 2019
Offline
 
johnmather
No, we fixed the underlying compatibility issue with glibc 2.34+.
I having the same issue with 19.5.773 ubuntu 22 latest crash at the starting

error: Crash report from raj; Houdini FX Version 19.5.773
Uptime 5 seconds
Fri Nov 3 19:55:01 2023
Caught signal 11

Traceback from 3279 ThreadId=0x7fd989b88e80
AP_Interface::coreDumpChaser(UTsignalHandlerArg) <libHoudiniUI.so>
AP_Interface::si_CrashHandler::chaser(UTsignalHandlerArg) <libHoudiniUI.so>
signalCallback(UTsignalHandlerArg) <libHoudiniUT.so>
UT_Signal::UT_ComboSignalHandler::operator()(int, siginfo_t*, void*) const <libHoudiniUT.so>
UT_Signal::processSignal(int, siginfo_t*, void*) <libHoudiniUT.so>
__sigaction <libc.so.6>
 Report
User Avatar
edward
Member
7871 posts
Joined: July 2005
Offline
 
You could try this in a Terminal window:

cd /opt/hfs19.5 # or wherever you installed houdini
source houdini_setup
houdini -foreground

Do you get the same OpenCL errors as OP in the terminal?
Edited by edward - Nov. 3, 2023 22:45:54
 Report
User Avatar
rmon61
Member
7 posts
Joined: March 2019
Offline
 
edward
You could try this in a Terminal window:

cd /opt/hfs19.5 # or wherever you installed houdini
source houdini_setup
houdini -foreground

Do you get the same OpenCL errors as OP in the terminal?

I able to fix by installing amd graphics drivers from the following link https://support.zivid.com/en/latest/getting-started/software-installation/gpu/install-opencl-drivers-ubuntu.html [support.zivid.com]
 Report
  • Quick Links