Comment 17 for bug 1134088

Revision history for this message
XXLRay (xxlray) wrote :

The memory allocation error even exists for small projects. Currently it's a nightmare. I open the project using the "Recent projects" menu, click on the timeline to find a cut position, make a cut, click on the timeline again to find the next cut and it crashes. Here is the typical output:

...
[mpeg @ 0x7fd154005ce0] max_analyze_duration 5000000 reached at 5000000
[mpeg @ 0x7fd154749980] max_analyze_duration 5000000 reached at 5000000
[swscaler @ 0x7fd156245fa0] Warning: data is not aligned! This can lead to a speedloss
on_tlbArrow_clicked called with self.GtkRadioToolButton
on_tlbRazor_clicked called with self.GtkRadioToolButton
[mpeg @ 0x2bc1c00] max_analyze_duration 5000000 reached at 5000000
[mpeg @ 0x4dd4800] max_analyze_duration 5000000 reached at 5000000
[mpeg @ 0x7fd1702edb00] max_analyze_duration 5000000 reached at 5000000
[mpeg @ 0x7fd1702f4960] max_analyze_duration 5000000 reached at 5000000
project state modified
state saved
Autosaving... before playback of new XML file.
Autosaving...
project saved! - Openshot_Tooltips
[mp3 @ 0x2f377a0] max_analyze_duration 5000000 reached at 5015510
[mp3 @ 0x2f377a0] Estimating duration from bitrate, this may be inaccurate
[mp3 @ 0x2effc80] max_analyze_duration 5000000 reached at 5015510
[mp3 @ 0x2effc80] Estimating duration from bitrate, this may be inaccurate
python: malloc.c:4254: malloc_consolidate: Assertion `nextchunk->fd_nextsize->bk_nextsize == nextchunk' failed.

Is the next_analyze duration reached thing something bad or the not alligned data? Is there any strace command I can execute to help you find the reason?