From: SourceForge.net <no...@so...> - 2007-11-25 20:47:03
|
Bugs item #1838190, was opened at 2007-11-25 14:37 Message generated for change (Comment added) made by dmmcintyr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104932&aid=1838190&group_id=4932 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: gui Group: None >Status: Closed >Resolution: Fixed Priority: 9 Private: No Submitted By: D. Michael McIntyre (dmmcintyr) >Assigned to: D. Michael McIntyre (dmmcintyr) Summary: Crash in countdown dialog Initial Comment: I can't reproduce a file from scratch that causes this problem, but I get the crash every time with the attached file. (Composition of one bar, two MIDI segments on one track.) Create new track, assign to audio, click the recording LEDs so audio track is recording, MIDI track isn't. Press record. Boom. Core was generated by `rosegarden /tmp/voices.rg'. Program terminated with signal 8, Arithmetic exception. #0 0x08773ac9 in Rosegarden::CountdownDialog::setElapsedTime (this=0x8eede18, elapsedSeconds=0) at /home/silvan/SVN/rosegarden/src/gui/dialogs/CountdownDialog.cpp:128 128 (elapsedSeconds * m_progressBarWidth) / m_totalTime; (gdb) bt #0 0x08773ac9 in Rosegarden::CountdownDialog::setElapsedTime (this=0x8eede18, elapsedSeconds=0) at /home/silvan/SVN/rosegarden/src/gui/dialogs/CountdownDialog.cpp:128 #1 0x08773b99 in Rosegarden::CountdownDialog::setTotalTime (this=0x8eede18, seconds=0) at /home/silvan/SVN/rosegarden/src/gui/dialogs/CountdownDialog.cpp:93 #2 0x0863810c in Rosegarden::SequenceManager::record (this=0x8ec0448, toggled=false) at /home/silvan/SVN/rosegarden/src/gui/seqmanager/SequenceManager.cpp:884 #3 0x083eaff4 in Rosegarden::RosegardenGUIApp::slotRecord (this=0x8c9db60) at /home/silvan/SVN/rosegarden/src/gui/application/RosegardenGUIApp.cpp:5199 #4 0x08407edc in Rosegarden::RosegardenGUIApp::qt_invoke (this=0x8c9db60, _id=199, _o=0xbf85098c) at /home/silvan/SVN/rosegarden/RGbuild/RosegardenGUIApp.moc:1006 #5 0xb7a53893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #6 0xb7a54338 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #7 0xb7de8907 in QButton::clicked () from /usr/lib/libqt-mt.so.3 #8 0xb7af1f8c in QButton::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3 #9 0xb7a8a681 in QWidget::event () from /usr/lib/libqt-mt.so.3 #10 0xb79eaaf0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #11 0xb79eccae in QApplication::notify () from /usr/lib/libqt-mt.so.3 #12 0xb755cca2 in KApplication::notify () from /usr/lib/libkdecore.so.4 #13 0xb797d27d in QApplication::sendSpontaneousEvent () from /usr/lib/libqt-mt.so.3 #14 0xb797bee2 in QETWidget::translateMouseEvent () from /usr/lib/libqt-mt.so.3 #15 0xb7979fcc in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3 #16 0xb79911a4 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #17 0xb7a051ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #18 0xb7a04fde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #19 0xb79ec699 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #20 0x083cfc32 in main (argc=2, argv=0xbf851754) at /home/silvan/SVN/rosegarden/src/gui/application/main.cpp:724 ---------------------------------------------------------------------- >Comment By: D. Michael McIntyre (dmmcintyr) Date: 2007-11-25 15:47 Message: Logged In: YES user_id=663564 Originator: YES That's what I did. I just wrote the followup comment in the commit log, not thinking. Oh well. Committed revision 8442. I can only get this to happen in one very isolated case, which I can't seem to get attached to this report due to SF problems. The fix I just committed only seems to fire in that one weird case, and anyway, isn't the whole countdown dialog something we no longer show, because it used to show time remaining to the end, and there is no longer an end? I think this is good enough. The RG_DEBUG message refers to this bug by number for further details, and it's such an isolated out there case anyway. I tried to reproduce it, and had trouble even getting the original file to screw up unless I followed my original steps in exactly the same order. It now fires off a FAILSAFE debug message and sets m_whatever to 1, and no more kaboom. That's probably sufficient, so I'm going ahead and closing. ---------------------------------------------------------------------- Comment By: Chris Cannam (cannam) Date: 2007-11-25 15:30 Message: Logged In: YES user_id=13489 Originator: NO Looks like simply checking m_totalTime for zero-ness, and not dividing by it if so, would probably be enough. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104932&aid=1838190&group_id=4932 |