On 3/20/19 4:53 PM, Will Godfrey wrote:
There seems to be a memory allocation problem that is triggered by deleting
tracks/sections. This has been there for quite a long time, but it has only
been a real problem for me lately because I'm doing a lot of quite heavy
editing, and have to resort to doing very frequent saves.
I recently saw a crash when deleting segments related to the undo
history. Couldn't reproduce it, though. And it only happened on exit.
I'm not certain, but I get the impression that the very fact of doing these
saves seems to reduce the likelihood of the crashes.
Memory issues are always tricky and can easily be exacerbated or
mitigated by almost anything.
Currently using build 15419, but as I said, it's been there a long time - years.
I'm not surprised. Last time I ran valgrind against rg there were
too many problems to even begin to track them all down. I gave up
because no one was complaining. That appears to have changed.
There are a number of ways you can help me track these down.
First would be to characterize the editing you are doing. Just a
list of the sorts of things, like track deletes that seem to cause the
issue. Also, how big are the compositions? Number of segments, tracks.
How many minutes? Does it happen even if you never play the composition?
Next, if you can analyze the core dumps for me when you crash, that
could be a big help. Though sometimes with memory issues, the stack
traces are useless. Have you worked with gdb and core dumps before?
Rosegarden-user mailing list
Rosegardenemail@example.com - use the link below to unsubscribe