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

Running install twice with Polymer hangs the process #1324

Closed
vladikoff opened this issue May 28, 2014 · 10 comments
Closed

Running install twice with Polymer hangs the process #1324

vladikoff opened this issue May 28, 2014 · 10 comments

Comments

@vladikoff
Copy link
Member

bower.json config:

{
  "name": "sample",
  "dependencies": {
    "polymer": "Polymer/polymer#~0.3.0",
    "core-menu": "Polymer/core-menu",
    "core-ajax": "Polymer/core-ajax"
  }
}

Running bower install once works properly, if you run bower install again the process will hang. If you leave it running for a while an error will appear:

~/tmp/so-23917177
$ bower install
FATAL ERROR: JS Allocation failed - process out of memory
Abort trap: 6

Details:

$ bower --version
1.3.3
$ npm version
{ http_parser: '1.0',
  node: '0.10.28',
  v8: '3.14.5.9',
  ares: '1.9.0-DEV',
  uv: '0.10.27',
  zlib: '1.2.3',
  modules: '11',
  openssl: '1.0.1g',
  npm: '1.3.26' }

From further testing it seems like the Polymer repo is affected.

@vladikoff vladikoff changed the title Running install twice hangs the process Running install twice hangs the process May 28, 2014
@sheerun
Copy link
Contributor

sheerun commented May 28, 2014

There's circular dependency error that is fixed on master but not yet released.

@vladikoff
Copy link
Member Author

Thanks @sheerun !

@vladikoff vladikoff changed the title Running install twice hangs the process Running install twice with Polymer hangs the process May 28, 2014
@silenceisgolden
Copy link

@sheerun This is what I was experiencing two weeks ago; I think its finally localized now. Can this be a hotfix? Thanks to you both for looking into this.

Edit: forgot to mention, [at least a partial] workaround seems to be adding a dependency to bower.json and running bower update.

@dfreedm
Copy link

dfreedm commented May 28, 2014

Is this a dupe of #1169?

@silenceisgolden
Copy link

@azakus yep, dupe

@vladikoff
Copy link
Member Author

Sure, #1169 seems to be tracking this

@dotnetwise
Copy link

This still happens!!

@JGSolutions
Copy link

Still not working for me either!

@dotnetwise
Copy link

someone please repoen it.

@sheerun
Copy link
Contributor

sheerun commented Oct 22, 2014

Works for me.

If it happens to you guys, please create new issue with environment info and steps to reproduce.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

6 participants