Closed GoogleCodeExporter closed 8 years ago
I don`t know what to say, except that you are the only one who reporting this
problem (atleast I didn`t heard anything similar).
And I don`t think that this is XviD4PSP fault. You can kill conhost process
right after starting encoding - all will work fine. So it seems like it needed
only for starting encoder process (run some_file.exe) and after that it not
used. Why it crashes - I don`t know. You can try to find some info about this
crash in the system log.
"2-pass x264 encoding of MPEG-2 into MKV"
Only with 2-pass encoding?
Only if the source file is MPEG2?
How "fast" it crashes (minimum time after starting encoding)?
Original comment by forc...@gmail.com
on 10 Oct 2010 at 12:11
I think that might be connected to the memory issue I experienced (issue #11).
I have been running out of memory constantly during the encoding (OS Memory low
warnings), so that might have been the reason of conhost failure. The last
encoding didn't suffer from the lack of free memory and the conhost didn't fail
even once, so the problem most probably is not Xvid4PSP directly.
Original comment by a.shpi...@gmail.com
on 11 Oct 2010 at 5:13
Today I experienced conhost crash again. The memory consumption of Xvid4PSP at
the moment of crash was ~1100Mb and the system had quite a while memory to
spare, so no 'Memory low' warning appeared.
As far as I understand that won't help you to identify the problem anyway, so
my question is if it's possible for encoding process to continue without
awaiting for the confirmation of conhost 'Close program' OS dialog box?
Answering on your questions:
1) I use only this type of conversion, and right now I am too short of time to
investigate other cases, sorry. May be later.
2) Usually it is 40-60 minutes from the start, but sometimes it happened after
4-6 hrs. I guess it is more dependent on the memory usage, or some kind of
system objects usage (GDI/handlers or whatever, I am not familiar with
WPF/.NET/whatever is guilty mechanics)
Original comment by a.shpi...@gmail.com
on 12 Oct 2010 at 5:09
[deleted comment]
I have a similar problem, so he's not the only one
Original comment by lwo...@gmail.com
on 14 Nov 2011 at 8:07
This behaviour is not reproduced with the currently latest version 5.10.305.0
(2012-09-13) RC32.1, so it can be closed.
Original comment by a.shpi...@gmail.com
on 19 Feb 2013 at 7:29
Original comment by forc...@gmail.com
on 20 Feb 2013 at 6:02
Original issue reported on code.google.com by
a.shpi...@gmail.com
on 10 Oct 2010 at 10:21Attachments: