#813 Rosegarden 1.0 hangs on my previously saved composition

gui (282)

I startet to notate my new composition (piano only) and
saved it to a rg file. If I now load this file,
rosegarden hangs (in an endless loop) and consumes 99%
cpu usage. But other files load fine. I compiled
rosegarden 1.0 on my 64bit gentoo with gcc 3.4.4, so
this may or may not be an 64bit issue. But I had no
problems so far and I hope I don't must type in all
this again... I attached my file so you can test if
this error occurs also in 32-bit rosegarden.


  • milde

    milde - 2005-10-02

    Rosegarden 1.0 hangs on this file on my linux.

  • Chris Cannam

    Chris Cannam - 2005-10-07

    Logged In: YES

    Confirmed with a 32-bit build of current CVS HEAD. Built
    with gcc-3.3.6 and qt-3.3.4, running with
    --nosequencer. Never seen this before, but it looks
    pretty serious. Traces etc to follow.

  • Chris Cannam

    Chris Cannam - 2005-10-07

    Logged In: YES

    OK, I'm having no luck attaching traces or anything --
    the site just doesn't seem to respond when I try to
    submit either an attachment or a lengthy comment. I'll
    take them to rg-devel instead.

  • D. Michael McIntyre

    Logged In: YES

    Not a 64-bit problem, most likely. I was saving a composition I had
    been working on for some time (and had saved previously countless
    times, and have been puttering with for a couple of days) when RG
    crashed. I wasn't able to get a stack trace. The autosave file is
    empty, so there's no recovering from this. This file causes exactly the
    same phenomenon you just described to occur.

    Boy, this sucks, doesn't it?

    There's NO WAY we can release until we figure this one out.

  • Chris Cannam

    Chris Cannam - 2005-10-15

    Logged In: YES


    There is a simple workaround.


    gunzip -c myfile.rg > myfile.xml

    and then run

    rosegarden myfile.xml

    The hang occurs in the compressed file read function in
    KDE (or Qt?). If you uncompress the file yourself,
    there's no opportunity for a problem, and fortunately
    Rosegarden can read the uncompressed versions too.

    This should at least give you an opportunity to export
    as Lilypond or MIDI, or maybe to hang in until we've
    actually worked out what the bug is.

    Needless to say, this doesn't diminish the severity of
    the bug.

  • D. Michael McIntyre

    Logged In: YES

    I loaded my unzipped file, saved it, and got a crash. Unfortunately, no
    core dump. I tried again, and tried several times to repeat the crash to
    no avail. It might be OK from here. Maybe. Fingers crossed. I think
    I'm going to hack out the compression on saving bit anyway for now,
    and save several backup versions of this along the way, and maybe
    curl my left pinkie toes and poke my tongue out the right side of my
    mouth and close my left eye while rubbing my head and clicking the
    save button.

  • Guillaume Laurent

    Logged In: YES

    Work-around in CVS.

  • Tommi Uimonen

    Tommi Uimonen - 2005-10-27

    Logged In: YES

    I've had a similar problem with autosaved file. Firstly rg
    crashed (for yet unkown reason), hence the autosaved file.
    And when rg tries to load the autosaved version, it just
    takes for ever and I have never waited to see if it finally
    would load it, rg just sits there consuming some cpu power
    (not 99%, but merely 50%)

    The interesting part:

    When I copied the autosaved version to other place with a
    normal name, it loads ok. Files are identical, but the
    autosaved loading did not manage to load it, while normal
    loading went ok.

  • D. Michael McIntyre

    Logged In: YES

    This is fixed, seems to work. Marking as pending so the tracker will
    automatically close it after some interval, unless the submitter has
    something to say to the contrary in the interim.

  • SourceForge Robot

    Logged In: YES

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).


Log in to post a comment.