Bug 722778 - [abrt] subtitleeditor-0.37.1-1.fc14: g_realloc: Process /usr/bin/subtitleeditor was killed by signal 6 (SIGABRT)
Summary: [abrt] subtitleeditor-0.37.1-1.fc14: g_realloc: Process /usr/bin/subtitleedit...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: subtitleeditor
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Martin Sourada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a24db4d03fd85eeac886135b30c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-17 17:34 UTC by Dirk Hoffmann
Modified: 2011-07-18 23:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-18 11:45:20 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (21.32 KB, text/plain)
2011-07-17 17:34 UTC, Dirk Hoffmann
no flags Details

Description Dirk Hoffmann 2011-07-17 17:34:27 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 21827 bytes
cmdline: subtitleeditor MaryPoppins.mpg
comment: Before going into investigating, please let us state what is the maximum allowed length for an MPG file that is going to be edited in the subtitleeditor. Mine is 4GB/>1h. If that is a principle problem, then we do not need to investigate.
component: subtitleeditor
Attached file: coredump, 1083637760 bytes
crash_function: g_realloc
executable: /usr/bin/subtitleeditor
kernel: 2.6.35.13-92.fc14.i686.PAE
package: subtitleeditor-0.37.1-1.fc14
rating: 4
reason: Process /usr/bin/subtitleeditor was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1310923132
uid: 500

How to reproduce
-----
1. Have an MPG file Movie.mpg (in MPG2)
2. "subtitleeditor Movie.mpg"
3. Movie file is several hours long (approx 4GB). Is that a problem?

Comment 1 Dirk Hoffmann 2011-07-17 17:34:30 UTC
Created attachment 513532 [details]
File: backtrace

Comment 2 Martin Sourada 2011-07-18 11:45:20 UTC
Thank you for filling the bug report. I have verified that this does not work (and it does not need to be an mpg video), but I also think that it isn't supposed to work because the command line argument is supposed to be a subtitle file, not a video file. You can open the video from inside the subtitle editor via Video->Open menu item. For opening the video from command line use

$ subtitleeditor -v <file-name>

Comment 3 Dirk Hoffmann 2011-07-18 23:38:54 UTC
(In reply to comment #2)
> but I also think that it isn't
> supposed to work because the command line argument is supposed to be a subtitle
> file, not a video file. You can open the video from inside the subtitle editor
> via Video->Open menu item. For opening the video from command line use
> 
> $ subtitleeditor -v <file-name>

Thank you. Yes, you are right: No problem when I open the video like this!

Probably the program should just close down in a more gentle way with an error message ("Input not a subtitle file" or "Format error in subtitle file" rather than a signal - which would always trigger a bug report).

Sorry, but a user error which triggers a bug report, is a ... bug! Please consider reopening it.


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