Bug 601706 - [abrt] crash in mkvtoolnix-3.3.0-1.fc13: Process /usr/bin/mkvmerge was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in mkvtoolnix-3.3.0-1.fc13: Process /usr/bin/mkvmerge was killed...
Alias: None
Product: Fedora
Classification: Fedora
Component: mkvtoolnix
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Dominik 'Rathann' Mierzejewski
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:e77ec0f22eb024376d0a9049b31...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-08 13:46 UTC by James Ettle
Modified: 2010-11-22 19:00 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2010-11-22 19:00:45 UTC

Attachments (Terms of Use)
File: backtrace (8.61 KB, text/plain)
2010-06-08 13:46 UTC, James Ettle
no flags Details

Description James Ettle 2010-06-08 13:46:16 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: mkvmerge -o 00002.MTS.mkv --forced-track 0:no -a 0 -D -S -T --no-global-tags --no-chapters ./m2ts2vpx.HBu0oDJB.ogg --default-track 1:no --forced-track 1:no --display-dimensions 1:1280x720 --fourcc 1:VP80 --default-duration 1:50fps -d 1 -A -S -T --no-global-tags --no-chapters ./m2ts2vpx.YZPli0i4.mkv --track-order 0:0,1:1 --cluster-length 500ms
comment: Ran command given in this bugreport.
component: mkvtoolnix
crash_function: libebml::EbmlMaster::FindFirstElt
executable: /usr/bin/mkvmerge
global_uuid: e77ec0f22eb024376d0a9049b3187a5b7bdbbfb2
package: mkvtoolnix-3.3.0-1.fc13
rating: 4
reason: Process /usr/bin/mkvmerge was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

Comment 1 James Ettle 2010-06-08 13:46:19 UTC
Created attachment 422199 [details]
File: backtrace

Comment 2 Dominik 'Rathann' Mierzejewski 2010-11-21 00:10:32 UTC
Could you upload those files somewhere? I cannot reproduce this.

Comment 3 James Ettle 2010-11-22 19:00:45 UTC
This bug pertains to a rather old mkvtoolnix, and I don't have it (or the media) any more. Nor have I encountered the bug. Closing accordingly.

Note You need to log in before you can comment on or make changes to this bug.