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

My browser got crashed with "Aw, Snap" error after upgrading to 3.4.8 #8690

Closed
dean-g opened this issue Aug 23, 2021 · 5 comments · Fixed by #8822
Closed

My browser got crashed with "Aw, Snap" error after upgrading to 3.4.8 #8690

dean-g opened this issue Aug 23, 2021 · 5 comments · Fixed by #8822
Assignees

Comments

@dean-g
Copy link

dean-g commented Aug 23, 2021

I have upgraded my "@apollo/client" from 3.3.21 to the 3.4.8 version.

Since then, my app got randomly crashed when the request payload is around 15KB. But the same worked well with the 3.3.21 version.

image

Can someone please help me fix this upgrade issue?

@j2L4e
Copy link

j2L4e commented Sep 1, 2021

We've been seeing (seemingly) random STATUS_BREAKPOINT, STATUS_ACCESS_VIOLATION, SIGILL and SIGSEGV errors since upgrading to 3.4.

Most of the time the same operation works right after hitting "reload", so I'm still to figure out how to reproduce this.

I was able to catch a single SIGILL that happened in lookupArray() in @wry/trie. But I have no idea if that's where stuff actually goes wrong or if it's just a side-effect of a different cause.

https://github.com/benjamn/wryware/blob/a675c8e4f592b334e66f5d1edc4ec686f89cc444/packages/trie/src/trie.ts#L29

@dean-g
Copy link
Author

dean-g commented Sep 1, 2021

it's happened to me when the request payload was around 15 to 20KB size!.

@benjamn
Copy link
Member

benjamn commented Sep 9, 2021

@dean-g @j2L4e Any chance you could take/share a heap snapshot before the crash?

@benjamn
Copy link
Member

benjamn commented Sep 20, 2021

Potentially related issue: #8784

@j2L4e
Copy link

j2L4e commented Sep 22, 2021

@benjamn very sorry to get back so late, would that snapshot still be of any use?

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.