Skip to content
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

Uncaught TypeError: Cannot delete property 'from' of function Uint8Array error in Android 6.0 and core-js 3.x #564

Closed
zaaack opened this issue May 25, 2019 · 8 comments

Comments

@zaaack
Copy link

zaaack commented May 25, 2019

Uncaught TypeError: Cannot delete property 'from' of function Uint8Array

this error comes from eithor exportStatic or exportProto

delete TypedArrayConstructor.prototype[KEY];

But it's normal in 2.6.5/

@zloirock
Copy link
Owner

Sorry, I can't reproduce it. It's tested in Android 6.0:

image

Could you add a reproducible example?

@zaaack
Copy link
Author

zaaack commented May 25, 2019

@zloirock Sorry, the error comes from user's report, and we didn't have an Android 6.0 device to reproduce, only an error message without error stack. I'll try find the reproducible code after install an android VM.

@zloirock
Copy link
Owner

zloirock commented Jun 2, 2019

Closed as can't reproduce. Waiting for a reproducible example to revisiting it.

@zloirock zloirock closed this as completed Jun 2, 2019
@treeandgrass
Copy link

i get same problem
array-buffer-view-core.js?ebb5:90 Uncaught TypeError: Cannot delete property 'from' of function Int8Array() { [native code] }

@simonbrent
Copy link

simonbrent commented Apr 28, 2021

I get the same, specifically from the line

delete TypedArrayConstructor[KEY];

This happens in the wild for certain pages of the website I work on, for users with Chrome 45. I have reproduced it using an old version of Chromium, downloaded from https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/338387/

@zloirock
Copy link
Owner

@simonbrent I haven't a Windows machine at hand, so I can't check it. But I know that this kind of bug is possible in some buggy engine versions. I'll add try / catch here, most likely it will help.

@simonbrent
Copy link

simonbrent commented Apr 28, 2021

@zloirock Thanks. I have tracked it further to any part of our site which uses d3-array, so I guess my next task will be to ask its maintainers to update, once you have released a fix :-) (dur, d3 don't depend on core-js)

zloirock added a commit that referenced this issue Apr 28, 2021
@simonbrent
Copy link

I can confirm that this fix solves the problem I was seeing. Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants