Thanks, Roland. When it happens next could you attach a new stack trace? (perhaps just 'apport-collect 726099' will upload the info). The stacktrace attached so far suggests that libc's malloc is at fault, so we may want to mark this bug as affecting libc as well. But I'd like to see if another stacktrace is identical, or randomly different.
Thanks, Roland. When it happens next could you attach a new stack trace? (perhaps just 'apport-collect 726099' will upload the info). The stacktrace attached so far suggests that libc's malloc is at fault, so we may want to mark this bug as affecting libc as well. But I'd like to see if another stacktrace is identical, or randomly different.