Menu
▾
▴
[Synfig-devl] [ synfig-Bugs-3034808 ] Double click canvas window built in close icon crash
|
From: SourceForge.net <no...@so...> - 2012-12-26 12:17:50
|
Bugs item #3034808, was opened at 2010-07-26 10:24 Message generated for change (Comment added) made by zelgadis_ksee You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=757416&aid=3034808&group_id=144022 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Crasher/nasty bug Group: GIT version Status: Open Resolution: None Priority: 5 Private: No Submitted By: Genete (genete) Assigned to: Genete (genete) Summary: Double click canvas window built in close icon crash Initial Comment: I accidentally double clicked the close icon on the canvas window. Synfig Studio crashed: synfigstudio: instance.cpp:366: void studio::Instance::close(): Assertion `iter!=studio::App::instance_list.end()' failed. ---------------------------------------------------------------------- Comment By: Konstantin Dmitriev (zelgadis_ksee) Date: 2012-12-26 04:17 Message: This bugtracker is no longer active. The issue is moved to the new bugtracker - http://synfig.org/issues/thebuggenie/synfig ---------------------------------------------------------------------- Comment By: Rene Sugar (renesugar) Date: 2010-10-05 09:39 Message: On Windows, if a crash is caused by a memory overwrite, you can sometimes find it by using the Windows' pageheap feature if your computer has enough memory to use it. Run gflags.exe in the Debugging Tools for Windows to turn on the feature. You need a computer with a lot of memory when using this feature since memory allocations occur on page boundaries. http://www.microsoft.com/whdc/devtools/debugging/default.mspx If you can reproduce the crash, another option is to set up the Debugging Tools for Windows on your computer and save a crash dump when you reproduce the crash. A crash dump file can be loaded into windbg for debugging the crash. On Linux, Valgrind is available for finding memory and threading errors. http://valgrind.org/ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=757416&aid=3034808&group_id=144022 |