P: Plugin crema causing generator to break

See https://www.adobeprerelease.com/
It may also help to email me directly with a list of people (email addresses) you'd like to be invited.  mcilroy - at - adobe.com

Thanks Cory, this would be great!

Eric, Adan, would you be willing to join the Photoshop Prerelease program so you can test with an advanced release of Photoshop?

Hi Cory, I believe this is the same error since we are navigating through smart objects and opening them and closing them with our scripts, this might be happening too fast for the engine

Danil, thanks for the details.  I was able to reproduce it, so we will investigate a fix.  Eric, it is not clear that this is the same issue (root cause) you are seeing.

Yeah, our script first renders video, and then saves start frames and end frames. Generator is crashing when saving the individual frames, which causes our script to stop working.. Do you have any idea of good timing for slowing it down?

Hi Eric,
if you open  some document and close it too fast, using any other plugin or script – there gonna be an "Unhandled property..." exception with "Unknown JavaScript error".

Hi Cory.

Thanks for the info about blacklisted plugin and unknown js error. I guess the self signed error is something on this end--Adan is aware of the issue, basically our plugin is not finding the location of our update server.

I turned up the log level of Generator to DEBUG. I'm seeing some more detail such as this one:

[warning:core 14:24:36.241 generator.js:133:30] Photoshop error Pipe write error: Error: EPIPE: broken pipe, write

This matches my experience that it will write the startframe, but not the endframe before Generator crashes.
 
I think we are probably going to have to strip down our plugin to something that's shareable with you. Not sure how much help I would be for that, since I didn't help on the development for this.

Thank you again!
Eric

Eric, 

1) The "blacklisted" error can be ignored.  That is caused by an old plugin which is no longer supported - but in some cases will be left on your machine from an old photoshop install. 
2) That is an unfortunately vague error.  In some cases (but not all) it can actually be harmless.  We are working to make that particular message more informative about the underlying cause.

I'm curious to hear more about the "self signing error".

Things to try:
1) Use a JS debugger to pause in generator.js 133
2) Change the log level in app.js
-    var _loggerManager = new logging.LoggerManager(logging.LOG_LEVEL_INFO),
+    var _loggerManager = new logging.LoggerManager(logging.LOG_LEVEL_DEBUG),
3) Provide me with a stripped down plugin with just the JPEG error case.

You may reach out to me directly by email if you need to provide non-public information:  {my last name} at adobe dot com.

As a side note: there is another more technical forum specifically for generator here:
https://groups.google.com/forum/#!forum/adobe-generator-dev
You my find it helpful for other questions/issues which may have been raised there before

Hi Cory.

Unfortunately, I can't share the plugins. I'm currently adding some console.log statements to our code to help track down exactly where it's failing.

I noticed some errors in the Generator log on launch of PS 2019 that I wondered if you  knew anything about them:
1) This plugin gives this error:

[error:app 09:50:01.536 app.js:309:37] Unable to load plugin at '/Library/Application Support/Adobe/Plug-Ins/CC/Generator/previewHD.generate': Plugin is blacklisted

When I remove that plugin, that error goes away. Not sure which version of Photoshop installed it since this machine used to have 2015, and currently has PS 2017 / 2018 / 2109 installed.

2) After our custom plugin loads, we get a self-signed warning and then this error:

[warning:core 09:50:03.400 generator.js:133:30] Photoshop error { id: 19, body: 'Unknown JavaScript error' }

Anyway, the main purpose of our custom plugin is to render out a PNG sequence of an animation. (It does this reliably in 2019). Then, it should save out the first and last frames as JPEGs, but it consistently crashes Generator in 2019 at this step.

Any ideas of things to test / try would be most appreciated.

Thanks!
Eric

EDIT: Looks like we still get the blacklisted and core warnings without our plugin loaded. I will do some playing around to see if unhandled property errors too.