Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Autodesk: Fix Loading Large Size Image Crash with hioOpenEXR #3332

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

erikaharrison-adsk
Copy link
Contributor

Description of Change(s)

In USD 24.08, the crash when loading an extreme-sized texture returns. The root cause is that now USD uses Hio_OpenEXRImage instead of HioOiio to load the exr images, and there are issues in OpenEXRCore & HioOpenEXR.

This solution is to fix loading large-size image crashes mainly resulting from int overflows.

Related: #3119

Fixes Issue(s)

  • N/A
  • I have verified that all unit tests pass with the proposed changes
  • I have submitted a signed Contributor License Agreement

@jesschimein
Copy link
Collaborator

Filed as internal issue #USD-10227

@jesschimein
Copy link
Collaborator

/AzurePipelines run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@meshula
Copy link
Member

meshula commented Oct 2, 2024

Thank you for these fixes. The changes to OpenEXRCore do not exist upstream, but the fixes are important enough that they should be upstreamed ~ we don't want the interned copy of OpenEXRCore to get ahead of the originating code with substantial changes like this. Could I ask that you also upstream the OpenEXRCore fixes to OpenEXR in parallel please? The OpenEXR test suite is supposed to be robust enough to catch very large files and so on, so could you also post at OpenEXR how to repro the failure? This should have been caught OpenEXR side :)

Thanks!

@adskWangl
Copy link
Contributor

Thank you for these fixes. The changes to OpenEXRCore do not exist upstream, but the fixes are important enough that they should be upstreamed ~ we don't want the interned copy of OpenEXRCore to get ahead of the originating code with substantial changes like this. Could I ask that you also upstream the OpenEXRCore fixes to OpenEXR in parallel please? The OpenEXR test suite is supposed to be robust enough to catch very large files and so on, so could you also post at OpenEXR how to repro the failure? This should have been caught OpenEXR side :)

Thanks!

Thank you for your response! I'll try to reproduce this failure with an independent OpenEXR case and upstream the OpenEXRCore fixes to OpenEXR as this fix is also important to us.

@jesschimein jesschimein added the blocked Issue fix or pull request blocked until questions are answered or pending notes are addressed label Nov 27, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
blocked Issue fix or pull request blocked until questions are answered or pending notes are addressed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants