-
Notifications
You must be signed in to change notification settings - Fork 19
Thumbnail should run before heavy processes so houdini does not crash #235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Thumbnail should run before heavy processes so houdini does not crash #235
Conversation
| """ | ||
| order = pyblish.api.ExtractorOrder + 0.49 | ||
| order = pyblish.api.ExtractorOrder + 0.25 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting to see this did fix it. Because I wonder what happens between +0.25 and +0.49.
I'd have expected this would needed to be negative like - 0.1 so that it'd run before ExtractROP - assuming that the crash had something to do with the heavy processed occurring from rendering heavy rops in the scene.
Also this plug-in does this check for whether thumbnails are already set on the instance:
thumbnail = instance.data.get("thumbnailPath")
if thumbnail:
# A thumbnail was already set for this instance
returnWe should ensure it doesn't now suddenly run BEFORE anything that we'd expect to otherwise set the thumbnail path - otherwise this one would incorrectly always take precedence.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In our case it failed on HDA extraction, therefor we moved it right in front of the HDA extractor. Do you have any other examples, where you could test this (sth. where you have the feeling the rop extractor fails)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ExtractActiveViewThumbnail is only affecting the workfile instance so we should consider only the plugins related to thumbnails and runs through workfile instance. like
There's another plugin in core but not related to workfile instance.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In our case it failed on HDA extraction, therefor we moved it right in front of the HDA extractor. Do you have any other examples, where you could test this (sth. where you have the feeling the rop extractor fails)?
How many HDAs were in your scene?
|
@SzabadosA could you create an issue for it and link it to this PR? |
sure: |
| """ | ||
| order = pyblish.api.ExtractorOrder + 0.49 | ||
| order = pyblish.api.ExtractorOrder - 0.25 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For information.
This order is smaller that the order of a plugin for extracting thumbnail and it runs over workfile instances.
Problem
We experienced segfault houdini crashes on thumbnail creation, when publishing products. This happens because heavy extractors (in our case the HDA extractor) still block the main thread at the moment when the process moves to the next extractor, which crashes the flipbook tool.
Changes
We change the extractor order to - 0.25 so the thumbnail executes before the HDA extractor, which mitigates the problem