Skip to main content
D
dan.robo
New Participant
April 21, 2020
Answered

AME crash introduced in 14.0.3 when using console es.executeScript

  • April 21, 2020
  • 2 replies
  • 5108 views

Using the following command caused AME to crash. 


"C:\Program Files\Adobe\Adobe Media Encoder 2020\Adobe Media Encoder.exe" --console es.executeScript "D:\TEST\test.jsx"

Contents of script
var a = "b";

 

It seems this issue was introduced in 14.0.3 as the crash doesn't happen if i roll back to 14.0.1.

14.1 - Crash
14.0.4 - Crash
14.0.3 - Crash
14.0.1 - Works

 

I've confirmed this happens on two seperate machines.

 

Crash Report

<?xml version="1.0"?>
<!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd">
<crashreport serviceVersion="2.7.0" clientVersion="2.7.0" applicationName="Adobe Media Encoder" applicationVersion="14.1" build="155" source="Windows-Client" crashType="CR_SIGNAL_SIGSEGV">
<time year="2020" month="4" day="21" hour="14" minute="54" second="32" timeoffset="0" timezone="GMT Daylight Time"/>
<user guid="0718823b-ecc4-4ea8-8100-180ff614bcc4"/>
<system platform="Windows 10 Pro" osversion="10.0" osbuild="18362" applicationlanguage="en-us" userlanguage="en-GB" oslanguage="en-US" ram="32540" machine="Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz" model="Intel64 Family 6 Model 158 Stepping 10" cpuCount="12" cpuType="8664" cpuFreq="2592 MHz"/>
<gpu>
<gpuinfo availability="Running/Full Power" adapterCompatibility="Intel Corporation" adapterRAM="1024 MB" caption="Intel(R) UHD Graphics 630" description="Intel(R) UHD Graphics 630" driverDate="20190925000000.000000-000" driverVersion="26.20.100.7262" videoModeDescription="2560 x 1440 x 4294967296 colors" pnpDeviceID="PCI&#92;VEN_8086&#38;DEV_3E9B&#38;SUBSYS_087D1028&#38;REV_00&#92;3&#38;11583659&#38;0&#38;10" installedDisplayDrivers="igd10iumd64.dll,igd12umd64.dll,igdumdim64.dll"/>
<gpuinfo availability="Off Line" adapterCompatibility="NVIDIA" adapterRAM="4095 MB" caption="NVIDIA Quadro P1000" description="NVIDIA Quadro P1000" driverDate="20191126000000.000000-000" driverVersion="26.21.14.4145" videoModeDescription="" pnpDeviceID="PCI&#92;VEN_10DE&#38;DEV_1CBB&#38;SUBSYS_087D1028&#38;REV_A1&#92;4&#38;44A1B07&#38;0&#38;0008" installedDisplayDrivers="nvldumdx.dll"/>
</gpu>
<crash exception="EXCEPTION_UNKNOWN" exceptionCode="0xc0000409" instruction="0x0000000048830D01">
<backtrace crashedThread="0">
<thread index="0">
<stackStatement index="0" address="0x00007FFFE71DC043" symbolname="seh_filter_exe"/>
<stackStatement index="1" address="0x000000014020D947" symbolname="ScriptLayer::ScriptObject::`default constructor closure&#39;"/>
<stackStatement index="2" address="0x00007FFFCE24C1C0" symbolname="_C_specific_handler"/>
<stackStatement index="3" address="0x00007FFFE9FA11CF" symbolname="_chkstk"/>
<stackStatement index="4" address="0x00007FFFE9F6A209" symbolname="RtlRaiseException"/>
<stackStatement index="5" address="0x00007FFFE9F9FE3E" symbolname="KiUserExceptionDispatcher"/>
<stackStatement index="6" address="0x00000000028C9E9D" symbolname="ScriptLayer::ExecuteScript"/>
<stackStatement index="7" address="0x00000000028CA41E" symbolname="ScriptLayer::ExecuteScriptFile"/>
<stackStatement index="8" address="0x00000000028B65B6" symbolname="ScriptLayer::GetAppScriptObject"/>
<stackStatement index="9" address="0x00000000047DBB3A" symbolname="dvacore::console::ExecuteCommand"/>
<stackStatement index="10" address="0x0000000140051AAE" symbolname="ScriptLayer::ScriptObject::`default constructor closure&#39;"/>
<stackStatement index="11" address="0x0000000140075245" symbolname="ScriptLayer::ScriptObject::`default constructor closure&#39;"/>
<stackStatement index="12" address="0x00000001401E82F6" symbolname="ScriptLayer::ScriptObject::`default constructor closure&#39;"/>
<stackStatement index="13" address="0x00007FFFE8137BD4" symbolname="BaseThreadInitThunk"/>
<stackStatement index="14" address="0x00007FFFE9F6CE51" symbolname="RtlUserThreadStart"/>
</thread>
</backtrace>
<registerSet>
<register name="RAX" value="0x0000000000000004"/>
<register name="RBX" value="0x0000000000000000"/>
<register name="RCX" value="0x0000000000001A3C"/>
<register name="RDX" value="0x0000000000000000"/>
<register name="RSI" value="0x0000000000000000"/>
<register name="RDI" value="0x000000000062E0E0"/>
<register name="RSP" value="0x000000000014DBB0"/>
<register name="RBP" value="0x000000000014DC40"/>
<register name="RIP" value="0x00007FFFE71DC043"/>
<register name="EFL" value="0x0000000000000246"/>
<register name="LastExceptionToRip" value="0x0000000000000000"/>
<register name="LastExceptionFromRip" value="0x0000000000000000"/>
</registerSet>

This topic has been closed for replies.
Correct answer Bruce Bullis

So the question is... why if Extend Script Tookit is working do I need to use something like the command line way? The reason is because the Extend Script Toolkit or VSCode way do not allow for any form of automation. Thanks


ExtendScript Toolkit was <EOL> years ago, but the ExtendScript Debugger for Microsoft Visual Studio Code (the recommended ExtendScript development environment) works great. CEP panels in AME allow for ExtendScript-driven automation .

AME command line scripting is definitely NOT a recommended approach. 

 

The bug discussed in this thread, DVAME-4198877, was fixed as of AME 22.5. 

2 replies

G
gretac78434027
New Participant
October 9, 2020

Crash also with 14.4. 

 

Do you know how to execute a script by command line but with media encoder already ?

 

thanks

Andrea

Bruce Bullis
Community Manager
Bruce BullisCommunity Manager
Community Manager
October 12, 2020

Just what you've already used:

 

"C:\Program Files\Adobe\Adobe Media Encoder 2020\Adobe Media Encoder.exe" --console es.executeScript "C:\Users\username\Desktop\test.jsx"

H
harryf58967104
Participating Frequently
May 5, 2021

Strange; reproduced the crash. We're tracking this as DVAME-4198877.


Hi Bruce,

 

Any chance someone's got to the bottom of this yet?

 

We're having the same issues in 15.1. We're running the .exe with "-console es.executeFile" and trying to run the below to add an AE comp to the the queue and kick it off:

app.getFrontend().addCompToBatch(pathToAEP, pathToEPR, pathToOutput);

var encoderHost = app.getEncoderHost();
encoderHost.runBatch();

while (encoderHost.isBatchRunning())
{
    app.wait(10000);
}
app.quit();

We see the same behaviour in that calling "es.executeFile" instead of "es.executeScript" opens without crashing but doesn't execute the script. (what's weird though is that it does execute the addCompToBatch function in 14.0.3 but then doesn't run "encoderHost.runBatch();" so we're still in the same situation. 15.1 just does nothing).

 

Any updates would be hugely appreciated!

 

Thanks in advance,

 

Harry

Bruce Bullis
Community Manager
Bruce BullisCommunity Manager
Community Manager
May 4, 2020

If you replace --executeScript (which expects a blob of ExtendScript to follow) with --executeFile (which expects a path to an ExtendScript file), the call works fine. 

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices