Bugs item #1677509, was opened at 2007-03-09 10:25 Message generated for change (Comment added) made by genete You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=757416&aid=1677509&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: None Group: None >Status: Closed >Resolution: Works For Me Priority: 5 Private: No Submitted By: dooglus (dooglus) Assigned to: Nobody/Anonymous (nobody) Summary: intermittant hang on quit Initial Comment: Sometimes when I attempt to quit synfigstudio, stdout shows: Application appears to have terminated successfuly but the programs doesn't exit. The 'Synfig Studio', 'Params, Timetrack, Layers, Keyframes', 'Tool Options' and other such windows stay on the screen, but no longer get repainted when exposed. Connecting to the process with gdb shows it is waiting on a mutex, here: #0 0xb7985189 in __lll_mutex_lock_wait () from /lib/tls/libpthread.so.0 #1 0xb7981f6d in _L_mutex_lock_29 () from /lib/tls/libpthread.so.0 #2 0x00000001 in ?? () #3 0xbfd4644c in ?? () #4 0xb6e6e028 in ?? () from /lib/tls/libc.so.6 #5 0xbfd463c8 in ?? () #6 0xb7d4d8d8 in ?? () from /usr/local/lib/libsynfig.so.0 #7 0xb6e6e0f8 in ?? () from /lib/tls/libc.so.6 #8 0xb6e6e028 in ?? () from /lib/tls/libc.so.6 #9 0xbfd463c8 in ?? () #10 0xb7c3e513 in synfig::Mutex::lock (this=0xb7f38080) at mutex.cpp:138 ---------------------------------------------------------------------- >Comment By: Genete (genete) Date: 2012-04-17 10:16 Message: Closing the bug since it is not reproducible since long time ago. If it comes back please reopen. ---------------------------------------------------------------------- Comment By: Paul Wise (pabs3) Date: 2008-05-19 22:28 Message: Logged In: YES user_id=35028 Originator: NO Have you seen this since 0.61.08? ---------------------------------------------------------------------- Comment By: dooglus (dooglus) Date: 2007-03-12 17:30 Message: Logged In: YES user_id=1546005 Originator: YES I just had the same crash happen again, with a very similar stack: (gdb) where #0 0xb7a1b189 in __lll_mutex_lock_wait () from /lib/tls/libpthread.so.0 #1 0xb7a17f6d in _L_mutex_lock_29 () from /lib/tls/libpthread.so.0 #2 0x00000001 in ?? () #3 0xbfa5015c in ?? () #4 0xb6f04028 in ?? () from /lib/tls/libc.so.6 #5 0xbfa500d8 in ?? () #6 0xb7de48dc in ?? () from /usr/local/lib/libsynfig.so.0 #7 0xb6f040f8 in ?? () from /lib/tls/libc.so.6 #8 0xb6f04028 in ?? () from /lib/tls/libc.so.6 #9 0xbfa500d8 in ?? () #10 0xb7cd4d7b in synfig::Mutex::lock (this=0xb7fcf080) at mutex.cpp:138 Backtrace stopped: previous frame inner to this frame (corrupt stack?) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=757416&aid=1677509&group_id=144022 ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Synfig-devl mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synfig-devl
