-
Notifications
You must be signed in to change notification settings - Fork 15.3k
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
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
Crash on app quit at atom::AtomCTDelegate::ClearCTExcludedHostsList #10051
Labels
Comments
Seeing this quite consistently (maybe 5% failure rate?) in our CI jobs |
facebook-github-bot
pushed a commit
to facebookarchive/nuclide
that referenced
this issue
Aug 18, 2017
Summary: Atom 1.19+ segfaults much more frequently during integration tests now. I've discovered the root cause (electron/electron#10051), but we probably won't get a fix for a while... This function gets called when a test exits *just as* a web request comes back - so I think this is happening when we try to make web requests in integration tests. I think it's fine if we just stub out all fetches in tests. It's not safe to assume that fetches are going to work on CI, anyway. Reviewed By: matthewwithanm Differential Revision: D5656739 fbshipit-source-id: e80d8a954bb7d6b4b928f3de29707d5232452e3d
tarruda
added a commit
that referenced
this issue
Nov 15, 2017
tarruda
added a commit
that referenced
this issue
Nov 15, 2017
tarruda
added a commit
that referenced
this issue
Nov 15, 2017
tarruda
added a commit
that referenced
this issue
Nov 16, 2017
tarruda
added a commit
that referenced
this issue
Nov 16, 2017
Move AtomCTDelegate to brightray as RequireCTDelegate and transfer ownership to brightray::URLRequestContextGetter. This fixes the wrong lifetime assumptions that result in AtomCTDelegate being used after free in some scenarios. Close #10051
tarruda
added a commit
that referenced
this issue
Nov 17, 2017
Move AtomCTDelegate to brightray as RequireCTDelegate and transfer ownership to brightray::URLRequestContextGetter. This fixes the wrong lifetime assumptions that result in AtomCTDelegate being used after free in some scenarios. Close #10051
tarruda
added a commit
that referenced
this issue
Nov 17, 2017
Move AtomCTDelegate to brightray as RequireCTDelegate and transfer ownership to brightray::URLRequestContextGetter. This fixes the wrong lifetime assumptions that result in AtomCTDelegate being used after free in some scenarios. Close #10051
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior
no crash on quit
Actual behavior
Crash on app quit
How to reproduce
No consistent repro. May be happening after #7651
cc: @kevinsawicki @deepak1556
The text was updated successfully, but these errors were encountered: