Flame 2025.2.3 on Rocky 9.5 Seg Faults

Sysadmins
1

Despite a couple rebuilds, we are seeing the same error occuring each time shortly after launching a project in Flame - this is regardless of differing project settings. This machine was previously running Flame 2023.3.2 on CentOS 7.6. To clarify, this error causes Flame to exit.

We get several SegFaults relating to the Autodesk Identity Manager as well as TangetHub- TangetHub being the final straw it would seem:

[Mon Aug 11 10:47:46 2025] AdskIdentityMan[7343]: segfault at 18 ip 00007f2f03a8f69c sp 00007f2edaff9150 error 4 in libc.so.6[7f2f03a28000+175000] likely on CPU 51 (core 3, socket 1)
[Mon Aug 11 10:47:46 2025] Code: 0f 11 07 0f 11 47 20 8b 06 8b 56 04 89 47 30 31 c0 85 d2 0f 95 c0 89 47 1c 31 c0 c3 66 90 f3 0f 1e fa 41 54 55 53 48 89 fb 90 <8b> 57 18 64 8b 04 25 d0 02 00 00 39 c2 0f 84 91 00 00 00 83 7f 30
[Mon Aug 11 10:47:47 2025] AdskIdentityMan[7373]: segfault at 18 ip 00007ff5f3e8f69c sp 00007ff5cb7fa150 error 4 in libc.so.6[7ff5f3e28000+175000] likely on CPU 2 (core 2, socket 0)
[Mon Aug 11 10:47:47 2025] Code: 0f 11 07 0f 11 47 20 8b 06 8b 56 04 89 47 30 31 c0 85 d2 0f 95 c0 89 47 1c 31 c0 c3 66 90 f3 0f 1e fa 41 54 55 53 48 89 fb 90 <8b> 57 18 64 8b 04 25 d0 02 00 00 39 c2 0f 84 91 00 00 00 83 7f 30
[Mon Aug 11 10:50:46 2025] rfkill: input handler enabled
[Mon Aug 11 10:50:50 2025] rfkill: input handler disabled
[Mon Aug 11 10:50:50 2025] nvidia-settings[8316]: segfault at 8 ip 00007f58b786dc1e sp 00007ffca6c46890 error 6 in libEGL.so.1.1.0[7f58b786c000+9000] likely on CPU 2 (core 2, socket 0)
[Mon Aug 11 10:50:50 2025] Code: 53 41 54 4c 8d 25 02 c8 00 00 55 48 89 fd 4c 89 e7 48 83 ec 08 ff 15 81 c8 00 00 48 8b 4d 20 48 8b 55 28 4c 89 e7 48 8d 45 20 <48> 89 51 08 48 89 0a 48 89 45 28 48 89 45 20 ff 15 6d c8 00 00 48
[Mon Aug 11 10:53:38 2025] TangentHub[5810]: segfault at 0 ip 00007ff4a3a9e0a5 sp 00007ffe85ebd210 error 4 in libc.so.6[7ff4a3a28000+175000] likely on CPU 53 (core 5, socket 1)
[Mon Aug 11 10:53:38 2025] Code: 0f

I was wondering if anyone had experienced anything similar or had any advice on the above? Anything would be greatly appreciated.

2

That’s a very strange series of errors in the log. A segmentation fault happens when the CPU tries to access a memory address that is invalid for its current context. Usually a result of a coding error or corrupted data.

To have multiple applications (identity manager, nvidia settings, and TangentMapper) in a short span all die of segmentation fault is highly unlikely on a healthy system. Multiple rare coding errors across apps would have to align to happen at the same time.

Based on that, this smells like hardware that is going bad (bad mainboard, faulty memory chip) or of an OS upgrade that has installed a common library that is not doing well. I don’t think that’s a Flame error, but a system hardware or OS install error.

It’s noteworthy that three of your four log entries identify libc.so as the failing code, which is a low level shared library of your C compiler. But there is also a reference to libEGL.so, thus not always the same path.

I’d try wipe the disk, run a memory and CPU test, reseat any cards (particularly GPU), maybe swpa slots if you can, and then install fresh and see how you fare.

2 Likes
3

Yea i too would vote for ram or even CPU, stuff can go faulty and its hard to diagnose.

I once had a logitec keyboard driver causing random crashes like that…

if the same sotware runs on a different machine its most likely hardware.

1 Like