# Silhouette 2024 on 2025.0.1 freezing flame **URL:** \ **Category:** Tools and Tech\ **Tags:** silhouette\ **Created:** [June 25, 2024, 6:27pm UTC](https://forum.logik.tv/t/silhouette-2024-on-2025-0-1-freezing-flame/10927 "2024-06-25T18:27:18Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![snacks](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/snacks/32/4834_2.png) [@snacks](https://forum.logik.tv/u/snacks)\ **Post date:** [June 25, 2024, 6:27pm UTC](https://forum.logik.tv/t/silhouette-2024-on-2025-0-1-freezing-flame/10927/1 "2024-06-25T18:27:18Z")
Anyone else having issues getting Silhouette 2024 to load via OFX? For some reason when I try to launch it, Flame freezes and I have to kill the terminal to get out. I seem to remember it autoloading in flame 2024 and the window just coming up, but I have to select the plug in now like mocha… I can run silhouette as a standalone, just not as an ofx. Rocky 9.3 I’ve tried installing the plugin and the standalone with dependencies. Not sure what else to do here… ---
**Author:** ![allklier](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/allklier/32/4309_2.png) [@allklier](https://forum.logik.tv/u/allklier)\ **Post date:** [June 25, 2024, 8:03pm UTC](https://forum.logik.tv/t/silhouette-2024-on-2025-0-1-freezing-flame/10927/2 "2024-06-25T20:03:58Z")
Yes, there was a bug a while ago, where it wouldn’t release some memory or something. But I thought that was fixed. Maybe @marcopaolini can provide insight? ---
**Author:** ![MLandon](https://avatars.discourse-cdn.com/v4/letter/m/e495f1/32.png) [@MLandon](https://forum.logik.tv/u/MLandon)\ **Post date:** [June 25, 2024, 8:38pm UTC](https://forum.logik.tv/t/silhouette-2024-on-2025-0-1-freezing-flame/10927/3 "2024-06-25T20:38:13Z")
I used to have an issue where I’d have to exit Flame after every time I used an instance of Silhouette in a Batch, otherwise Flame would freeze up. I haven’t had that issue in the last couple of Silhouette releases though. I assume they fixed the memory leak. ---
**Author:** ![snacks](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/snacks/32/4834_2.png) [@snacks](https://forum.logik.tv/u/snacks)\ **Post date:** [June 25, 2024, 8:46pm UTC](https://forum.logik.tv/t/silhouette-2024-on-2025-0-1-freezing-flame/10927/4 "2024-06-25T20:46:28Z")
It’s the weirdest thing. You hit the Open Silhouette Interface button and it just locks everything down. I’m working with Boris support on this, but I’ll let you all know what I find out. ---
**Author:** ![marcopaolini](https://avatars.discourse-cdn.com/v4/letter/m/59ef9b/32.png) [@marcopaolini](https://forum.logik.tv/u/marcopaolini)\ **Post date:** [June 26, 2024, 12:22am UTC](https://forum.logik.tv/t/silhouette-2024-on-2025-0-1-freezing-flame/10927/5 "2024-06-26T00:22:47Z")
We are attempting to reproduce the hang on the same setup. Will report back. ---
**Author:** ![marcopaolini](https://avatars.discourse-cdn.com/v4/letter/m/59ef9b/32.png) [@marcopaolini](https://forum.logik.tv/u/marcopaolini)\ **Post date:** [June 26, 2024, 6:13pm UTC](https://forum.logik.tv/t/silhouette-2024-on-2025-0-1-freezing-flame/10927/6 "2024-06-26T18:13:41Z")
@snacks Can you provide me with the following logs from /Home/.cache/BorisFX/ Silhouette 2024 after the hang occurs: silhouette.log, plugin-flame.log and server-flame.log? ---
**Author:** ![snacks](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/snacks/32/4834_2.png) [@snacks](https://forum.logik.tv/u/snacks)\ **Post date:** [June 26, 2024, 6:46pm UTC](https://forum.logik.tv/t/silhouette-2024-on-2025-0-1-freezing-flame/10927/7 "2024-06-26T18:46:51Z")
Sure thing. I’ve been working with Victor and he has them as well. Attached. plugin-flame.log is a 0kb file with nothing in it. Here are the other two. Also having issues with SynthEyes. I get this when I try to launch it: [root@vxfhost SynthEyes]# ./SynthEyes.sh Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: ManageChildProcess failed (t=0.608066) [GFX1-]: glxtest: ManageChildProcess failed Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: ManageChildProcess failed (t=0.608066) |[1][GFX1-]: glxtest: X error, error\_code=10, request\_code=152, minor\_code=5 (t=0.608088) [GFX1-]: glxtest: X error, error\_code=10, request\_code=152, minor\_code=5 (SynthEyes:740948): GtkGLExt-CRITICAL \*\*: 14:21:09.451: gtk\_widget\_set\_gl\_capability: assertion ‘GDK\_IS\_GL\_CONFIG (glconfig)’ failed (SynthEyes:740948): Gdk-ERROR \*_: 14:21:09.452: The program ‘SynthEyes’ received an X Window System error. This probably reflects a bug in the program. The error was ‘GLXBadContext’. (Details: serial 3487 error\_code 158 request\_code 152 minor\_code 6) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk\_x\_error() function.) ./SynthEyes.sh: line 34: 740948 Trace/breakpoint trap (core dumped) ./SynthEyes $_ [root@vxfhost SynthEyes]# [ERROR viaduct::backend::ffi] Missing HTTP status [ERROR viaduct::backend::ffi] Missing HTTP status ^C [Archive.zip](https://forum.logik.tv/uploads/short-url/ci4X7mNRgnT0euyHbeW1XVlsA5q.zip) (3.3 KB) ---
**Author:** ![philm](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/philm/32/9286_2.png) [@philm](https://forum.logik.tv/u/philm)\ **Post date:** [June 26, 2024, 6:59pm UTC](https://forum.logik.tv/t/silhouette-2024-on-2025-0-1-freezing-flame/10927/8 "2024-06-26T18:59:44Z")
This might be a silly question but is there any detriment to using the root user, and the subsequent ownership of files? ---
**Author:** ![snacks](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/snacks/32/4834_2.png) [@snacks](https://forum.logik.tv/u/snacks)\ **Post date:** [June 26, 2024, 7:18pm UTC](https://forum.logik.tv/t/silhouette-2024-on-2025-0-1-freezing-flame/10927/9 "2024-06-26T19:18:39Z")
I tried both root and user and get the same errors… ugh… ---
**Author:** ![marcopaolini](https://avatars.discourse-cdn.com/v4/letter/m/59ef9b/32.png) [@marcopaolini](https://forum.logik.tv/u/marcopaolini)\ **Post date:** [June 27, 2024, 4:41pm UTC](https://forum.logik.tv/t/silhouette-2024-on-2025-0-1-freezing-flame/10927/10 "2024-06-27T16:41:16Z")
@snacks We can reproduce the issue here with Flame 2025.0.1 running in Rocky 9.3 and are working on a solution. The issue seems to be specific to Rocky 9.3 as Silhouette 2024 runs as expected in both Flame 2024 and 2025 both in Rocky 8. ---
**Author:** ![snacks](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/snacks/32/4834_2.png) [@snacks](https://forum.logik.tv/u/snacks)\ **Post date:** [June 27, 2024, 4:55pm UTC](https://forum.logik.tv/t/silhouette-2024-on-2025-0-1-freezing-flame/10927/11 "2024-06-27T16:55:24Z")
Thanks, Marco. I appreciate the update and confirmation that I’m not crazy. Victor has been helping me out with some Syntheyes issues as well. When it rains, it pours.