-
Notifications
You must be signed in to change notification settings - Fork 1.7k
I just updated the SDK and now pub upgrade
just prints "Segmentation fault"
#23930
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
Comments
Thanks Günter - it is not hugely surprising, the bots are crashing left and right when testing using pub - I think this is an vm issue, but it does not happen on every commit (i.e., we occasionally see green lines, and then lines where pub crashes on 100% of tests). I will take a quick look |
@iposva-google @munificent don't know if this is a vm or pub issues (from the flakiness I am guessing vm), stack from gdb below. This seems to flake on the bots (not 100% sure it is not the involved cls). I can easily reproduce locally, we run out of stack when reading the snapshot it seems:
|
cc @turnidge Todd and I saw this yesterday. Just running If a non-debug build is helpful, let me know. |
The only way to get this stack trace (and stack overflow) is with a recursive generic type, i.e. with a type whose type argument is pointing back to itself (not illegal per se), and doing so without a TypeRef breaking the cycle (bug). So this type is probably not finalized. It would really help to have a repro in debug mode. |
A temporary fix for this has been submitted to work around the problem while we investigate the root cause. |
https://codereview.chromium.org/1276753002/ was submitted to fix this issue. |
Dart VM version: 1.12.0-edge.8a3e1345024648861b26f634a944f0811b418319 (Thu Jul 30 15:51:12 2015) on "linux_x64"
The text was updated successfully, but these errors were encountered: