Search Unity

  1. Unity Asset Manager is now available in public beta. Try it out now and join the conversation here in the forums.
    Dismiss Notice

Bug (Case 1403906) [WebGL][Safari] RuntimeError: Out of bounds memory access (evaluating 'dynCall_v.call

Discussion in '2022.1 Beta' started by matt_cauldron, Feb 17, 2022.

Thread Status:
Not open for further replies.
  1. matt_cauldron

    matt_cauldron

    Joined:
    Dec 17, 2021
    Posts:
    48
    Hello,

    Building a fairly simple WebGL project upgraded from 2020, on Safari - consistently get this memory access error

    Screenshot 2022-02-17 at 09.29.58.png

    Repro'd on 2022.1.0b8

    This doesn't reproduce with Chrome, so I assume it is a WebGL x Safari specific issue
    This doesn't reproduce on Unity 2020

    Case: 1403906

    Thanks!

    Matt
     
    Last edited: Feb 17, 2022
    LeonhardP likes this.
  2. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,136
    Hi @matt_cauldron,

    Thanks for the bug report. We'll look into it.
     
    matt_cauldron likes this.
  3. matt_cauldron

    matt_cauldron

    Joined:
    Dec 17, 2021
    Posts:
    48
  4. matt_cauldron

    matt_cauldron

    Joined:
    Dec 17, 2021
    Posts:
    48
    Hi @LeonhardP is there any eta or indication of where this bug is in the prioritised backlog for the 2022 beta?
     
  5. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,136
    It's with the developers but there's no ETA for a fix I could share at this time.
     
  6. robrab2000-aa

    robrab2000-aa

    Joined:
    Feb 8, 2019
    Posts:
    117
    We seem to be facing this issue too. Are there any updates on finding a fix or workaround?
     
  7. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,136
    Hi @robrab2000-aa,

    The issue that was discussed in this thread was due to a problem with Safari 15.4 (on macOS or on iOS). Upgrading to macOS 12.4 (to Safari 15.5) fixes this issue.

    Safari issue was https://bugs.webkit.org/show_bug.cgi?id=237180

    If this doesn't apply to you, you're likely facing a different issue. In that case, please submit a new bug report. Closing this thread since the original issue here has been resolved.
     
Thread Status:
Not open for further replies.