Re: Motion error -12792
Re: Motion error -12792
- Subject: Re: Motion error -12792
- From: Bret Battey <email@hidden>
- Date: Tue, 26 Sep 2017 09:08:21 +0000
- Thread-topic: Motion error -12792
Thanks Darrin,
That’s a very helpful clarification — I will start taking a look at what is
happening with disk / memory swap in particular.
Actually, the ‘no such plugin’ error occurs well after when the Critical Alert
was generated, so I will assume for now that it is just a product of a very
confused/hung machine which I was attempting to wake up…
-=Bret
From: Darrin Cardani <email@hidden<mailto:email@hidden>>
Date: Monday, 25 September 2017 at 17:48
To: Bret Battey <email@hidden<mailto:email@hidden>>
Cc: "email@hidden<mailto:email@hidden>"
<email@hidden<mailto:email@hidden>>
Subject: Re: Motion error -12792
The specific error you’re seeing: -12792, is a timeout error. This usually
occurs when writing out a frame takes an excessively long time (longer than 2
minutes). Note that this doesn’t mean that rendering the frame takes longer
than 2 minutes, just that writing it to disk does. Things that could cause this
include the system running low on memory and spending a lot of time swapping,
having a really slow disk, and other applications that are also writing to it
at the same time, etc. If the disk is mounted over the network and has lost its
network connection, that would also do it. So I don’t think that part of your
problem has to do with your FxPlug.
The second part is saying that your plug-in wasn’t found by PlugInKit, so it
could not load it. Was the error in the console printed at the same time as the
export error occurred? I ask because the apps don’t generally try to load
plug-ins at any time other than startup, so I would have expected to see that
message when the application was launched rather than during an export.
Darrin
On Sep 24, 2017, at 6:19 AM, Bret Battey
<email@hidden<mailto:email@hidden>> wrote:
I am wondering if anyone here has a list of the Motion Critical Alert error
numbers and corresponding message. With my FxPlug, after several hours of
rendering it can fail with this message from Motion:
Export Failed
The operation could not be completed because an error occurred while exporting
(error -12792)
I suspect that this will merely correspond to the following in the Console, but
I could always hope that the error code points to some additional/different
clue, to what is otherwise probably going to be a very tough bug to track down.
Motion[613:181959] [ops] readyPlugIns failed:Error Domain=PlugInKit Code=4 "no
such plugin (uuid not found)" UserInfo={NSLocalizedDescription=no such plugin
(uuid not found)}
2017-09-23 11:28:30.236470+0100 Motion[613:181959] [ops] plug-in <PKPlugin:
0x107f23ce0 OptiNelder(1.1) B8AB7AC8-8207-4F5E-B7D0-7BEFB2F72155 3(0)
/Volumes/BatData/bretbattey/Library/Developer/Xcode/DerivedData/OptiNelder-cucoecnycarcxldlqejbxhfmlvcu/Build/Products/Debug/OptiNelder.app/Contents/PlugIns/OptiNelder.pluginkit>
pre-screen sees activating state
-=Bret
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list
(email@hidden<mailto:email@hidden>)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden<mailto:email@hidden>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden