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

Pub fails due to bad auto-update #20565

Closed
DartBot opened this issue Aug 18, 2014 · 23 comments
Closed

Pub fails due to bad auto-update #20565

DartBot opened this issue Aug 18, 2014 · 23 comments
Assignees
Labels
P1 A high priority bug; for example, a single project is unusable or has many test failures
Milestone

Comments

@DartBot
Copy link

DartBot commented Aug 18, 2014

This issue was originally filed by Sebastian.G...@gmail.com


What steps will reproduce the problem?

  1. Install Dart Editor version 1.6.0.dev_09_03 (DEV)
  2. Run pub get

What is the expected output? What do you see instead?

Expected:
Working Pub Get

Actual:
Pub get failed, [3] vm\object.cc:17891: error: Fatal error in Array::New: invalid len -6

What version of the product are you using?

  • Dev Channel Dart Editor
  • Dart Editor version 1.6.0.dev_09_03 (DEV)

On what operating system?
Windows 7 Professional


Attachment:
darteditor.png (5.47 KB)

@DartBot
Copy link
Author

DartBot commented Aug 18, 2014

This comment was originally written by Sebastian.Gerske...@gmail.com


Correct Build Version of Dart Editor:

Dart Editor (DEV) build 39285

@floitschG
Copy link
Contributor

Added Area-Pub, Triaged labels.

@nex3
Copy link
Member

nex3 commented Aug 18, 2014

This is definitely a VM error.


Removed Area-Pub label.
Added Area-VM label.

@iposva-google
Copy link
Contributor

Zach, can you please work with Sebastian to get the setup which is trying to allocate an array of length -6?


Set owner to @zanderso.
Removed Priority-Unassigned label.
Added Priority-High, Accepted labels.

@zanderso
Copy link
Member

I could not reproduce on Linux. Is it possible to share more detailed reproduction steps, e.g. a project on github or similar, or does this happen with every "pub get" on Windows?


Added NeedsInfo label.

@DartBot
Copy link
Author

DartBot commented Aug 18, 2014

This comment was originally written by Don.J.Olm...@gmail.com


It doesn't happen on Linux. It happens in Windows. I'm hitting this same issue and had to downgrade my SDK.

@DartBot
Copy link
Author

DartBot commented Aug 18, 2014

This comment was originally written by Sebastian.G...@gmail.com


It happens on no specific Project. It happens during every Pub operation (Get, Upgrade, Serve).

Iam using Windows x64 and a x64 Dart Editor. I Updated to bleeding edge today and it works.

@zanderso
Copy link
Member

I've begun investigating on Windows.


Added Started label.

@DartBot
Copy link
Author

DartBot commented Aug 19, 2014

This comment was originally written by @bp74


I have accidentally opened a duplicate issue #20588.
It also happens if you start pub without arguments.
And it only happens on 1 of 3 PCs i'm using (all with Windows 7 64 bit).

@zanderso
Copy link
Member

Bernhard, Don, Sebastian,

We're having a bit of trouble reproducing on Windows. Would one or more of you be willing to put a different dart.exe in your sdk folder so we can try to get a stack trace?

Thanks!

@DartBot
Copy link
Author

DartBot commented Aug 19, 2014

This comment was originally written by Adam.Kimmorl...@gmail.com


I've just started getting this error too after upgrading. I'm on Windows 8 x64 though. I'm happy to put a different dart.exe in my sdk and send you a stack trace if it helps.

@floitschG
Copy link
Contributor

Issue #20588 has been merged into this issue.

@DartBot
Copy link
Author

DartBot commented Aug 20, 2014

This comment was originally written by @bp74


@Zra: sure please send me the other dart.exe and i will try it. But unfortunately i won't be at the PC where it crashes for the next couple of hours.

@zanderso
Copy link
Member

Please try dropping this dart.exe into your sdk bin directory. It should generate a dart stack trace before failing as before.


Attachment:
dart.exe (8.05 MB)

@DartBot
Copy link
Author

DartBot commented Aug 21, 2014

This comment was originally written by @bp74


Okay done. I don't know if it is good or bad news - but it runs perfectly fine with the new executable. I have reverted the dart.exe and the old one still fails.

@iposva-google
Copy link
Contributor

Bernhard, could you try with the latest built bit (not officially released yet) and report? Ideally you can install this one side-by-side with the failing setup. Thanks!

Bits are available here: http://gsdview.appspot.com/dart-archive/channels/dev/signed/39442/editor/

@DartBot
Copy link
Author

DartBot commented Aug 21, 2014

This comment was originally written by @bp74


Here are the results, i also downloaded 1.6.0-dev.9.5 ...

1.6.0-dev.9.3: CRASH
1.6.0-dev.9.5: NO ERROR (the latest available build from the dev channel)
1.6.0-dev.9.6: NO ERROR (the link you have sent me)

So it seems the error is gone, at least on my PC.

@zanderso
Copy link
Member

Bernhard, could you try to collect a core dump for us? Running pub from the command line, after the assertion fails, but before clicking away the crash dialog:
1.) Run the Task Manager
2.) Right click on dart.exe
3.) Select "Create Dump File"

Thanks!

@DartBot
Copy link
Author

DartBot commented Aug 21, 2014

This comment was originally written by @bp74


Here is something very strange! I have downloaded the zip-file of build 39285 which should be 1.6.0-dev.9.3 right? The big surprise is that this one is working too!

The dart.exe from the new download is 8462336 bytes in size.
The dart.exe from the old download is 8393728 bytes in size.

To be clear, both versions are 1.6.0-dev.9.3 but the one that is failing was an auto update from 1.6.0-dev.8.0 i think.

@DartBot DartBot added Type-Defect P1 A high priority bug; for example, a single project is unusable or has many test failures labels Aug 21, 2014
@DartBot DartBot added this to the 1.7 milestone Aug 21, 2014
@nex3
Copy link
Member

nex3 commented Sep 1, 2015

@mit-mit Why did you assign this back to pub?

@sethladd
Copy link
Contributor

sethladd commented Sep 1, 2015

Aside: should we remove the label Area-Pub, now that pub has its own repo?

@nex3
Copy link
Member

nex3 commented Sep 1, 2015

Yes please!

@mit-mit
Copy link
Member

mit-mit commented Sep 2, 2015

I deprecated Area-Tools as it had a bunch of active issues no one was actually paying attention to. The majority of those were infrastructure issues that I moved to Area-Infra, but there were just a few like this that needed to go somewhere else.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 A high priority bug; for example, a single project is unusable or has many test failures
Projects
None yet
Development

No branches or pull requests

8 participants