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.

Sign up for GitHub

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

Jump to bottom

Possible v8 cache bug #395

Closed
guybedford opened this issue May 18, 2019 · 1 comment
Closed

Possible v8 cache bug #395

guybedford opened this issue May 18, 2019 · 1 comment
Labels
bug Something isn't working

Comments

@guybedford
Copy link
Contributor

The next.js testing revealed a possible v8 cache bug with a CI failure on Azure on Node.js 10 with that was resolved by opting out of the v8 cache.

Without being able to directly diagnose this v8 bug, it may be worthwhile to disable the cache entirely, as the minor perf benefit doesn't seem worth exposing a possible v8 bug to users.
@guybedford guybedford added the bug Something isn't working label May 18, 2019
This was referenced May 22, 2019
Closed
Merged
@guybedford
Copy link
Contributor Author

Resolved in #404.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Disable v8cache in ncc build vercel/ncc
1 participant
@guybedford