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

Safari 9 Compatibility (Mavericks) #4

Closed
asoksevil opened this issue Dec 6, 2016 · 3 comments
Closed

Safari 9 Compatibility (Mavericks) #4

asoksevil opened this issue Dec 6, 2016 · 3 comments
Labels

Comments

@asoksevil
Copy link

asoksevil commented Dec 6, 2016

Describe the issue

It crashes right after installing it. You have to manually delete it from the extensions folder since it will make Safari crash upon opening.

One or more specific URLs where the issue occurs

[URL(s) for issue on a specific site are mandatory]

Screenshot in which the issue can be seen

[Screenshot(s) for visual issues are mandatory]

Steps for anyone to reproduce the issue

  1. Install on Safari 9 on Mavericks

Your settings

[If you fail to provide this info, I will mark the issue as invalid. Lists all settings which differs from default settings]

  • Safari version: 9.1.3
  • uBlock Origin version: 1.10.0-alpha.1
  • MacOS version: 10.9.5
Your filter lists

[Example: "Default filter lists + FRA", or "Default filter lists minus uBlock -- Badware risks"]

Your custom filters (if any)
@Foiled56
Copy link

Foiled56 commented Dec 7, 2016

Heres a quick video explaining how to fix your problem

@el1t
Copy link
Owner

el1t commented Dec 8, 2016

I've been looking into this, seems like uBlock 0.9.5.2 has a similar issue where it throws an error—it just doesn't crash the browser. Occurs when reading third-party assets that are shipped with the extension (readRepoCopyAsset) if the resource is not in cache. Still investigating.

@el1t el1t added the bug label Dec 8, 2016
@el1t el1t closed this as completed in 1db5dab Dec 9, 2016
@asoksevil
Copy link
Author

@el1t Yeah, I've been using 0.9.5.2 for a while and it works pretty well (didn't know it was crashing)

Now that it has been fixed, I'll keep trying it.

Thanks!

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

No branches or pull requests

3 participants