Testing an update for ogmtools, see bug 6352 I created a sample.ogm from an avi file. Ogminfo gives good info. The file is 212Mb $ ogmsplit -s 100 sample.ogm (ogmsplit.cpp) First pass: finding split points. This may take a while. Get something to drink. FATAL: could not allocate -1984626431 bytes of memory.
Assignee: bugsquad => oliver.bgr
$ ogmsplit -s 110 sample.ogm (ogmsplit.cpp) First pass: finding split points. This may take a while. Get something to drink. FATAL: could not allocate -1984626431 bytes of memory. $ ogmsplit -s 50 sample.ogm (ogmsplit.cpp) First pass: finding split points. This may take a while. Get something to drink. FATAL: could not allocate -1984626431 bytes of memory. The -s setting doesn't seem to make any difference. There are various old references to similar problems on a quick google search. $ ogmsplit -t 300 -n 3 sample.ogm (ogmsplit.cpp) First pass: finding split points. This may take a while. Get something to drink. FATAL: could not allocate -1984626431 bytes of memory. Seems broken.
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Valid Mga3
Version: 2 => 3
Whiteboard: (none) => MGA2TOO
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD