9 Nov
2014
9 Nov
'14
12:41 p.m.
Did anyone have this error before, typically at the end of encodings?
- Carsten
8:32 p.m.
Am 09.11.2014 um 21:21 schrieb Carl Hetherington:
Hi Carsten,
I haven't seen it, but then I rarely use Windows. What version? Is
it repeatable?
It's the guy who still uses DVD-o-matic, and this reoccurring crash of DCP-o-matic
seems to be the reason he still does. I pointed him to the last test version, and it
crashed again. I do assume it is a problem with his installation. But maybe also old
preferences? Does DCP-o-matic reads old DVD-o-matic prefs?
Anyway - it is WIN7-64 on an i7 notebook, and he had that issue with previous versions of
DCP-o-matic before. He told me it always occurs around the end of the encoding, and that
subsequent encodings always seem to get a bit further towards the end, but apparently he
never managed to get through completely.
Maybe look at the logfile?
- Carsten
11:34 p.m.
On Sun, 9 Nov 2014, Carsten Kurz wrote:
Am 09.11.2014 um 21:21 schrieb Carl Hetherington:
> Hi Carsten,
>
> I haven't seen it, but then I rarely use Windows. What version? Is
> it repeatable?
It's the guy who still uses DVD-o-matic, and this
reoccurring crash of
DCP-o-matic seems to be the reason he still does. I pointed him to the
last test version, and it crashed again. I do assume it is a problem
with his installation. But maybe also old preferences? Does DCP-o-matic
reads old DVD-o-matic prefs?
It does, yes. I've just removed that, as it is not well-tested and seems
not to be very useful any more. If he could test 1.76.12 that would
eliminate the old config files as a potential source of the problem.
Anyway - it is WIN7-64 on an i7 notebook, and he had
that issue with
previous versions of DCP-o-matic before. He told me it always occurs
around the end of the encoding, and that subsequent encodings always
seem to get a bit further towards the end, but apparently he never
managed to get through completely.
Strange. 1.76.12 also has slightly improved error reporting in that it
might (I'm not sure) drop a file called "backtrace.txt" into the film's
directory when that crash occurs. That file might be useful for me to
look at. The log file would also be good, if that's available.
Thanks,
Carl
11:41 p.m.
Am 10.11.2014 um 00:34 schrieb Carl Hetherington:
Strange. 1.76.12 also has slightly improved error
reporting in that it
might (I'm not sure) drop a file called "backtrace.txt" into the film's
directory when that crash occurs. That file might be useful for me to
look at. The log file would also be good, if that's available.
He is reading this and may try to salvage those files.
- Carsten
10 Nov
10 Nov
9:29 p.m.
Am 10.11.2014 um 00:34 schrieb Carl Hetherington:
Strange. 1.76.12 also has slightly improved error reporting in that it
might (I'm not sure) drop a file called "backtrace.txt" into the film's
directory when that crash occurs. That file might be useful for me to
look at. The log file would also be good, if that's available.
I don't know if that Visual C++ error message is a clear hint towards VC++ as the
source of the problem - but, I have never seen any special prerequisites regarding this
library for DCP-o-matic. I notice that my WIN7-64Pro Laptop has a couple of them installed
- 2005 WIN32+WIN64, 2008 with various version numbers, etc. I can see there are more
recent versions of it available on the net for download.
Is there a way to get a grip on these versions and dependencies? Does DCP-o-matic install
it's own version or depend on one specific version?
- Carsten
9:49 p.m.
On Mon, 10 Nov 2014 22:29:52 +0100
Carsten Kurz <audiovisual(a)t-online.de> wrote:
Am 10.11.2014 um 00:34 schrieb Carl Hetherington:
It's almost certainly an uncaught exception or other error in
DCP-o-matic, and probably nothing to do with Visual C++ (it's not even
built with Visual C++, it's just using its runtime libraries AFAICT).
It's just hard to get at the root cause on Windows... the hacks in
1.76.12 might help if the crash is repeatable (with luck, the
backtrace.txt file gives clues as to what was happening when it
crashed).
Regards,
Carl
Strange. 1.76.12 also has slightly improved error reporting in
that it might (I'm not sure) drop a file called "backtrace.txt"
into the film's directory when that crash occurs. That file might
be useful for me to look at. The log file would also be good, if
that's available.
I don't know if that Visual C++ error message is a clear hint towards
VC++ as the source of the problem - but, I have never seen any
special prerequisites regarding this library for DCP-o-matic. I
notice that my WIN7-64Pro Laptop has a couple of them installed -
2005 WIN32+WIN64, 2008 with various version numbers, etc. I can see
there are more recent versions of it available on the net for
download.
4 Dec
4 Dec
9:21 a.m.
Am 09.11.2014 um 21:21 schrieb Carl Hetherington:
Hi Carsten,
I haven't seen it, but then I rarely use Windows. What version? Is
it repeatable?
Oops - now this friend of mine was the initial source of that screenshot - today, for the
first time ever, I experienced it myself:
As with him, it occured at 99%. I restarted dcp-o-matic and just hit 'Make DCP'
again. I rushed through the files, but crashed again at the end.
I'll send over the log and metadata file to you personally, Carl.
- Carsten
3797
days inactive
3822
days old
7 comments
2 participants
participants (2)
-
Carl Hetherington -
Carsten Kurz