mmg crashes after 10s with fortify: longjmp causes uninitialized stack frame

Bug #1014236 reported by MMlosh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mkvtoolnix (Ubuntu)
New
Undecided
Unassigned

Bug Description

MKVtoolnix's gui crashes 10s + 190ms ater launch (yes, it crashes on a timer).
*** longjmp causes uninitialized stack frame ***: mmg terminated (in libc: __fortify_fail)
It does happen only under unusual conditions, but a stack corruption is a serious problem anyway.

Conditions:
Enabled checking of new version (on by default - Why?? Filled as bug #1014229)
New version has to be checked (set last_check=0 in ~/.config/mkvtoolnix/config to be sure)
Unreachable DNS servers
    This was caused by a crashed server in my case.
    Unplugging the network cable from the computer works (unless networmanager is used - the interface&routes need to stay up, so the packets are blackholed instead of returning hard errors)
    The sure way is probably "echo nameserver {IP} >/etc/resolv.conf", while {IP} is an unused IP address on local network.

All done on 64b ubuntu Precise.

console output will be attached immediately,
strace output if requested.

PS: I don't understand why gnome-keyring appears on the memory map.

Revision history for this message
MMlosh (mmlosh) wrote :
description: updated
description: updated
Revision history for this message
Moritz Bunkus (moritz-bunkus) wrote :
Revision history for this message
MMlosh (mmlosh) wrote :

It may be very similar.
But this one happens under different conditions.

Also they claim that one has been solved for a year.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.