I got a strange bug, where synfig crashes everytime I add a line for orientation. When I click the line then to try and drag it to the correct location, synfig will crash. Tried it a couple times, but always the same.
open new project
click somewhere in the ruler
an orientation line will appear
click the line
synfig crashes, needs to restart
This is very unfortunate, because I can’t use orientation-lines at all now. Any workaround?
Not sure if the bug reports fit 100% because they talk about instant-crash when dragging the ruler. It is similar, but for me I just clicked the ruler, not drag, so Synfig did not crash instead showed the guide line. Only when I click the guide line, crash happens. Still, I tried dragging the ruler and it also crashed. Both problems are very unforunate. I have commented bug #805
I know it’s a shame … but i do’nt have that kind of OS … Is it possible someone publish traces of the bug like the one published in the first message of the 805 bug report. I’m mainly interrested in call stack
Does that crash when you click ? drag ? or release ? or both ?
Don’t worry, I am a bit ashamed that I DO have that kind of OS. However I’d be glad to provide any additional information, but I am not sure how to see and copy the call stack that you are interested in. Is it in some kind of log file? Let me know how I can access it, then I will gladly post it here.
Synfig crashes when I click the guide line (mouse button release, not yet on press) Actually drag works, I never tried it, but again when I release the mouse button, crash. Also, when I drag the ruler (before release)
Ah okay, you see I was describing for Windows 8.1 myself I don’t have OS X or Linux here.
edit: I am not sure how to get the call stack, I thought this was only possible for developers, not for users of software. I clicked around and figured out, the program is written in C++, so I will click more to find a crash analysis tool for that. Let’s see if a mere user can help somehow after all.
OK so I found some things in the Windows Event Log, namely a message for every time Synfig crashed, with a lot or some detalis at least, not as many as that guy in the bug report showed, but here goes nothing:
Crash when clicking (releasing) guide-line:
Protokollname: Application
Quelle: Application Error
Datum: 06.02.2016 19:36:14
Ereignis-ID: 1000
Aufgabenkategorie:(100)
Ebene: Fehler
Schlüsselwörter:Klassisch
Benutzer: Nicht zutreffend
Computer: CountFluffy
Beschreibung:
Name der fehlerhaften Anwendung: synfigstudio.exe, Version: 0.0.0.0, Zeitstempel: 0x56168fce
Name des fehlerhaften Moduls: synfigstudio.exe, Version: 0.0.0.0, Zeitstempel: 0x56168fce
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000335e7c
ID des fehlerhaften Prozesses: 0x1038
Startzeit der fehlerhaften Anwendung: 0x01d1610d29c849f2
Pfad der fehlerhaften Anwendung: C:\Program Files\Synfig\bin\synfigstudio.exe
Pfad des fehlerhaften Moduls: C:\Program Files\Synfig\bin\synfigstudio.exe
Berichtskennung: 802d3827-cd00-11e5-be95-74d435557a28
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-02-06T18:36:14.000000000Z" />
<EventRecordID>36632</EventRecordID>
<Channel>Application</Channel>
<Computer>CountFluffy</Computer>
<Security />
</System>
<EventData>
<Data>synfigstudio.exe</Data>
<Data>0.0.0.0</Data>
<Data>56168fce</Data>
<Data>synfigstudio.exe</Data>
<Data>0.0.0.0</Data>
<Data>56168fce</Data>
<Data>c0000005</Data>
<Data>0000000000335e7c</Data>
<Data>1038</Data>
<Data>01d1610d29c849f2</Data>
<Data>C:\Program Files\Synfig\bin\synfigstudio.exe</Data>
<Data>C:\Program Files\Synfig\bin\synfigstudio.exe</Data>
<Data>802d3827-cd00-11e5-be95-74d435557a28</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
Crash when dragging ruler:
Protokollname: Application
Quelle: Application Error
Datum: 06.02.2016 19:40:18
Ereignis-ID: 1000
Aufgabenkategorie:(100)
Ebene: Fehler
Schlüsselwörter:Klassisch
Benutzer: Nicht zutreffend
Computer: CountFluffy
Beschreibung:
Name der fehlerhaften Anwendung: synfigstudio.exe, Version: 0.0.0.0, Zeitstempel: 0x56168fce
Name des fehlerhaften Moduls: synfigstudio.exe, Version: 0.0.0.0, Zeitstempel: 0x56168fce
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000338450
ID des fehlerhaften Prozesses: 0x25c
Startzeit der fehlerhaften Anwendung: 0x01d1610dd1b991c8
Pfad der fehlerhaften Anwendung: C:\Program Files\Synfig\bin\synfigstudio.exe
Pfad des fehlerhaften Moduls: C:\Program Files\Synfig\bin\synfigstudio.exe
Berichtskennung: 114e0285-cd01-11e5-be95-74d435557a28
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-02-06T18:40:18.000000000Z" />
<EventRecordID>36634</EventRecordID>
<Channel>Application</Channel>
<Computer>CountFluffy</Computer>
<Security />
</System>
<EventData>
<Data>synfigstudio.exe</Data>
<Data>0.0.0.0</Data>
<Data>56168fce</Data>
<Data>synfigstudio.exe</Data>
<Data>0.0.0.0</Data>
<Data>56168fce</Data>
<Data>c0000005</Data>
<Data>0000000000338450</Data>
<Data>25c</Data>
<Data>01d1610dd1b991c8</Data>
<Data>C:\Program Files\Synfig\bin\synfigstudio.exe</Data>
<Data>C:\Program Files\Synfig\bin\synfigstudio.exe</Data>
<Data>114e0285-cd01-11e5-be95-74d435557a28</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
Sorry its German. Not sure if you can add more information to that report, that is all I saw. Maybe you as the C++ developer need to tell Windows what to include there? That’s the spirit I got from the link above. What else was weird: Usually when a program crashes, Windows asks me if they should send the report to Microsoft. But when your program crashes, that window is a bit different, does not ask that question, simply collects some data and figures out that the problem could not be solved, the program needs to be closed, and I will be informed if any news arrive… ?!
EDIT: My bad, everything works fine, all the guide work properly, from ruler or directly in drawing area
My build output was done in a wrong directory
Thanks Jérôme you did it
Original erroneous message
[size=85]Still Crashing.
It seems it emits a GDK_BUTTON_RELEASE just under the modified line when moving around in the ruler WHILE keeping the button pressed.
In case of button release while the guide is already in drawingarea, it crashes too [double y(event->button.y),x(event->button.x); around line 2120][/size]