-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Low runner "createBuffer" error on iOS #654
Comments
Correction: I've just received the same error for an Android device. After checking again I found two other earlier reports of this error from Android devices. So, it is not just iOS as I had incorrectly stated earlier, but no PCs or Macs have reported this error. |
Is this the line you are saying the error is firing on?
|
Yes. Apparently, in rare situations on iOS and (even rarer) on Android, the value of |
Are you 100% it is referencing that line? A few lines above it already checks if self.ctx is set, so I'm not sure how it could possibly be null at that line. |
Yes, I'm sure. That is the only line in the source that calls Yes, there is a null check performed on |
After placing some log traces in the Howler code I now see the cause of the problem: The call to It appears the problem can be fixed by adding a null check after the call to
|
BTW, The bug is still there :(. |
Yes, fixed with #1363, waiting for a merge |
Hello, we're currently experiencing this error in some very specific situations on iOS Safari. As a temp fix in addition to the MR above, I'm setting |
I am getting lots of null errors from inside the unlock function, different to the error above. somehow ctx is valid when the touch handlers are added but not later when executed. |
Maybe an up here? My pr has been opened for half a year now.. |
We're also seeing this issue pop up sporadically, would be awesome #1363 could get merged or another similar fix. @goldfire and/or any other contributors able to weigh in here? While it might not be the same 'root cause', we are also seeing the following, which feels very similar to this issue:
I haven't done any deeper tracing to identify the specifics of it at this stage, as it's only affecting a small number of Safari users at this stage. While it may not be related to this, when googling for the error I stumbled across the following, which sounds similar (though probably not as useful as the explicit tracing done in #654 (comment)): |
@0xdevalias I also see the suspend issue. Always Safari. |
I am receiving reports of the following error from the field:
null is not an object (evaluating 'e.ctx.createBuffer')
. The error occurs in Howler 2.0.1 (minified) when running the following code:The error appears to be coming from line 263 in howler.js (unminified).
The error only occurs on iOS devices, and it occurs for much less than 1% of iOS devices. However, devices that generate the error tend to generate it again in future sessions. I have been seeing the error for a number of months (it is not new to v2.0.1). I cannot recreate the error on my iPad.
If you need more information then I can add code to gather additional data when the error occurs. Just let me know what you would need.
The text was updated successfully, but these errors were encountered: