[go: nahoru, domu]

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

VSCode.ShipIt Service could not initialize xpcproxy #10718

Closed
jayphelps opened this issue Aug 19, 2016 · 4 comments
Closed

VSCode.ShipIt Service could not initialize xpcproxy #10718

jayphelps opened this issue Aug 19, 2016 · 4 comments
Labels
info-needed Issue requires more information from poster

Comments

@jayphelps
Copy link
jayphelps commented Aug 19, 2016
  • VSCode Version: 1.3.1
  • OS Version: Mac OS X 10.11.5

Every two seconds I'm receiving these in the system Console:

8/19/16 12:30:55.476 PM com.apple.xpc.launchd[1]: (com.microsoft.VSCode.ShipIt[18008]) Service could not initialize: 15F34: xpcproxy + 12684 [1462][F7717708-ACF7-307D-B04E-998DFC36598F]: 0xd
8/19/16 12:30:55.476 PM com.apple.xpc.launchd[1]: (com.microsoft.VSCode.ShipIt) Service only ran for 0 seconds. Pushing respawn out by 2 seconds.

I assume this isn't normal that xpcproxy is crashing. I'm fairly new to vscode so I haven't noticed any particular feature not working except I cannot update vscode without manually going to the website and getting a new binary, but it sounds like #3520 is the cause of that.

@alexdima
Copy link
Member

@weinand @joaomoreno any ideas -- I could not find "com.microsoft.VSCode.ShipIt" in our sources

@joaomoreno
Copy link
Member

Check electron/electron#5139. I assume you have tried restarting your machine?

@joaomoreno joaomoreno added the info-needed Issue requires more information from poster label Aug 22, 2016
@jayphelps
Copy link
Author

@joaomoreno yep, I've restarted three times since then. No change. Interesting that they also could not update and had the same symptoms as me. When I attempt to update, the app closes and does not start back up, when I start it again it had not updated.

If this is firmly believed to be an electron issue, obviously I can move this over to there.

@joaomoreno
Copy link
Member

Definitely sounds dupe of #3520. You can also reach out to the Electron folks, I'd be interested in knowing if they figure it out.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

3 participants