-
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
SymbolBucket.prototype.isEmpty throws TypeErrors on startup #3663
Comments
I get this error a lot since updating I believe to v0.27.0, happens in quick succession too. For instance, I'll get 10-15 errors exactly like that at once. I get this error on all browsers on my 2015 MacBook Pro so don't think its to do with device speed, at least for me. EDIT: Here's my Chrome stack trace. Not very useful I know...
|
I am encountering a similar issue updating from v25.0.1 to v0.27.0 or v0.28.0. In my case, this error got thrown out after Map#setFilter was called and it does not happen if I don't call Map#setFilter. For instance, I have a mousemove event listener which handle hover effect on a symbol layer (which would call Map#setFilter when a symbol is being hovered). After a few calls of Map#setFilter (approximately 4 to 5 calls), this error would be thrown consecutively a couple of times (from 4 - 1x times randomly). Error captured in Chrome:
|
+1, Same issue here! |
mapbox-gl-js version: Master
SymbolBucket randomly (roughly 1 out of 10 times) throws errors on startup. It is probably a race condition as I've only seen it happen on slower devices (iPhone 5s) which might be triggered by a map resize during map initialization. Everything seems to be working fine when the map is running.
Error:
Offending code:
The safari inspector is kind enough to not provide stack traces for this error 😢 , I'll keep looking for a proper stack trace.
Expected Behavior
Errors should not be thrown.
Actual Behavior
Errors are thrown.
The text was updated successfully, but these errors were encountered: