gnomebaker assert failure: *** glibc detected *** gnomebaker: free(): invalid pointer: 0x092b1318 ***

[Olivier Jeulin]

Binary package hint: gnomebaker

I had 2 crashes while adding hundred of files to a new DVD, each time when the max capacity of the DVD is getting close to the max, the CPU runs at 100% for 2-5 seconds, then the program crashes.

Scenario:
I'm adding files to a new empty DVD : changed the name, created 1 folder, inserted hundred of files (about 60% of the 4.7GB are occupied). I created a second folder, added files, more than 4.7Go, I removed some files to get about 100Mo free on the DVD.
I added files until there was 47MB free (if I remember correctly), then 16Mo free. When I added 3 more files the program crashed.
Files are 6-8MB (JPEGs)

ProblemType: Crash
Architecture: i386
AssertionMessage: *** glibc detected *** gnomebaker: free(): invalid pointer: 0x092b1318 ***
Date: Sat Nov 7 23:28:08 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnomebaker
Package: gnomebaker 0.6.4-1
ProcCmdline: gnomebaker
ProcEnviron:
 LANGUAGE=fr_FR.UTF-8
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Signal: 6
SourcePackage: gnomebaker
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
Title: gnomebaker assert failure: *** glibc detected *** gnomebaker: free(): invalid pointer: 0x092b1318 ***
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin mail plugdev video

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #476008, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.