OK, I have a more official fix, please give it a try:
So a possible workaround is to suggest the following to users 1. Open the file(Mac): “/Applications/Adobe ExtendScript Toolkit CC/ExtendScript Toolkit.app/Contents/SharedSupport/Required/cdic/11BTBackend.jsx” 2. Search for the value: 604800000 (line reads bt.timeout = 604800000) 3. Replace that value with 604800 and save 4. Quit ExtendScript Toolkit and relaunch. |
A handful of third-party developers have verified this works.
Here's the cause of the error:
It looks like an issue because of signed 32-bit integer overflow that happens on this date “19 Nov 2018”. In the implementation in the ESTK jsx file “/Applications/Adobe ExtendScript Toolkit CC/ExtendScript Toolkit.app/Contents/SharedSupport/Required/cdic/11BTBackend.jsx”, there is a timeout specified in milliseconds “bt.timeout = 604800000; // a week in milliseconds”. The current time is(time(NULL)) since EPOCH: 1542783918 seconds. Adding: 1542783918 + 604800000 = 2147583918(which crosses the range of 32 bit integer(2,147,483,647).) Looks like it was a mistake putting 3 zeroes at the end because in BridgeTalk code... it expects timeout in seconds and not milliseconds. So bt.timeout should be 604800 and that will fix the overflow issue. |
AdChoices