Like @rodolforg I can’t reproduce Synfig crashing on WINE too.
@huddybuddy321 Can you do the following:
The final output might be informative (…or might not)
I just tried it here and it works fine 
Sadly, on Windows, GUI apps does not have any stdout/stdin/cerr/cout/cin/cerr.
He should edit the .bat launch file in Notepad to launch with --console. He could do it by changing this line:
start “” “%~dp0\bin\synfigstudio.exe”
to
start “” “%~dp0\bin\synfigstudio.exe” --console
<could be>
Also It could be an issue of capricious graphic driver, depending the format of pixel in memory where hovered.
Try to change settings like bits per pixels (16,24,32…) and change graphic acceleration of GFX card.
If possible upgrade your driver 
</could be>
I can reproduce the crash. Unfortunately, when I open a cmd, go to the studio directory, and enter “synfigstudio.exe --console”, then when the crash comes, the console window crashes together with the program so I don’t have a chance to read what it says.
On a pure hunch: Synfig used to be quite stable under Windows for a long time. Then suddenly, around version 1.2, lots of versions appeared that crashed all the time for the feeblest reasons, even for just pulling down a guideline. Version followed version but the Windows problem never improved. In all the cases, Synfig didn’t manage to write any “death message”, and it never had any autosave to show either.
If I remember correctly, it turned out at long last that the transition from gtk2 to gtk3 was responsible for the trouble. The Windows version of the new kit kept throwing unexpected exceptions from the bowels of its code; these exceptions weren’t handled within Synfig and made the whole program crash.
Then someone issued a huge monster change where he diligently and laboriously encapsuled each and every d*mn gtk3 call with a try clause, and Synfig returned to normal under Windows again. (This is more or less hearsay; I don’t know the details; I’m not part of the programming team.)
The current symptoms remind me very much of that flaky Windows situation.
Soooo, might it remoootely be possible that some code flow is still left somewhere that calls the colour picker and has not been protected by a try?
@huddybuddy321 @PeterGB do you use dual monitor setup? I read on Google search some people complaining on this case.
Yes, I use dual monitor. I’ll update you on if unplugging my second monitor fixes the issue.
I uploaded my draft for a new Color Editor I mentioned on another post.
Could you try it and see if it crashes too? Here is my work-in-progress: WIP [Synfig Studio] new color editor by rodolforg · Pull Request #2095 · synfig/synfig · GitHub . Windows users can test by following these steps. PS: As I just uploaded the code, you may have to wait some minutes.
Hello again. Any news?
Sorry, I took a break. I can confirm, unplugging my second monitor does fix the issue.
I have the same issue with Synfig crashing immediately upon using the color picker, moving to a color I want, then clicking on the color. It always crashes Synfig.
Link to video of issue
I need both monitors so hopefully there is a solution for this. Thanks so much for any assistance.
But it works fine with a single monitor? Just for checking the cause of the issue
Thank you for responding so quickly. Disconnecting the 2nd monitor fixes the issue and it no longer crashes with the color picker.
Hopefully someone can find a way to make it work when both monitors are being used.
I have a dual monitor and turned one off, which fixed the color picker crashes. However, it continues to crash (except for the color picker) so I used your method and got the following errors (before it crashed).
See screenshot…
I navigated to the to the folder on freedesktop.org but do not know what to do with these files. I am running Synfig 1.5.1 64bit on Windows 10 (updated).
Sadly it doesn’t say what happened. It isn’t the issue that crashes Synfig.
Thanks for taking a look.
I have the same issue in Debian 12. Dual monitor. Dual CPU/GPU Nvidia + Cuda Nvidia drivers. Synfig 1.5.
But in my case, I don’t think it’s related to Synfig. I have crashes in other apps requiring high graphical ressources since last kernel update too, So I think it’s a Nvidia drivers issue not up-to-date to kernel in my case.
But I can relate that the crash happens with color picker too.
I don’t know if this is a real fix yet for Synfig crashing, but I switched from using Chrome to using Firefox when watching YouTube. I know Chrome can be a memory pig at times.
I have been trying to learn Synfig with my dual monitor (Synfig on one, Youtube Tutorials on the other) but it kept crashing. So I rebooted (once again) but this time opened YouTube in Firefox, leaving both monitors running.
So far, after one day Synfig has not crashed once!
It used to crash a few times an hour.
Someone else may want to try this and let us know.
@gdhorning: Maybe one is usinge hardware acceleration while the other doesn’t
@cr77: Do your both screens use the smae resolution and are they aligned on the same line (up/down) ?
In answer to your questions…
Also…
No, they are both 16:9 ratio, but not same resolution and aligned only at bottom (see Prime display scr_).
I use Synfig in 3840*2160 monitor, it’s a secondary screen but used as primary in Gnome config.
And I’m aware my config is quite specific, it’s Prime config for Optimus management by Nvidia drivers.
