-
Notifications
You must be signed in to change notification settings - Fork 356
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
Bus error in OS X 10.9 #204
Comments
Sounds like an error upstream that will need to be addressed by https://github.com/joyent/libuv (or may have already). We can't fix that error from this plugin so I recommend staying on OSX 10.8 until node catches up. |
Got the same issue; OS X 10.8.5
|
@spacenick Oh really? Which version of node.js? |
Oops yea sorry, node v0.10.18 |
Thanks! Still nothing we can likely do to fix that from here. I haven't ran into this issue and I'm on the same setup. If you can, creating a test repo that recreates the error would be much helpful. It was helpful in tracking down this previous watch error: nodejs/node-v0.x-archive#5463 |
Thanks @shama |
@spacenick Thanks; I assumed this was a 10.9 issue. Downgrading to node 0.10.17 fixed this for me. |
Same issue with OSX 10.9, simple watch some
OSX DP5 |
Thank you @varju, fix this problem downgrading to node 0.10.17 |
Thanks, @varju. Downgrading to 0.10.17 fixed it for me, too. Here's how you downgrade to node 0.10.17 using homebrew:
You can list all available node versions using |
Should this still be open? I feel like 10.9/Node 10.2 should be supported... Just not possible? |
Sure, I'll reopen but there isn't anything we can do to fix or avoid this issue here. We'll probably just have to wait for a fix upstream. |
After upgrading to OSX 10.9 I installed Node v0.10.21 and things started working again for me. |
After my initial OSX upgrade to 10.9, it failed. |
I also just installed Mavericks, which caused this error to start happening for me. Upgrading Node to v0.10.21 resolved the issue. |
Same as @jasford. Upgraded to 0.10.21 and it works again |
Same here, just upgraded :) On Oct 22, 2013, at 4:06 PM, Adam Savitzky notifications@github.com wrote:
|
0.10.21 looks good to me too. |
Thank you everyone! Closing with the recommendation of upgrading node to |
The fact that there was so much activity here for the OSX upgrade makes me glad that I chose grunt as my build tool! |
Yep, sorry for throwing a huff earlier — "downgrade" as a solution feels lame, but "upgrade" is fine with me :) On Oct 22, 2013, at 4:57 PM, Andy notifications@github.com wrote:
|
I had the same issues. I have a feeling this is going to be a popular topic next couple of weeks :) On top of that - I had installed Node with the .pkg installer instead of brew, so I used this answer on SO to uninstall Node: http://stackoverflow.com/a/17203692/853685 and then followed the steps above to install 0.10.21 and everything works fine now :) |
I had the same error. Updated node from |
I'd suggest staying away from brew for node... Use NVM(Node version manager) to manage your node installs: https://github.com/creationix/nvm Super easy to use, and you can just use curl to install it:
|
Upgrading to node v0.10.21 does the trick |
Just updated to node v.0.10.21 and it works now. Thanks for reporting @mcranston18 :D |
Working flawlessly now. Thanks guys. |
Upgrading Node, via Brew, to 0.10.21 fixed this issue for me. OSX 10.9. |
Yep, node v0.10.21 fixes it. |
Same here, thanks! |
Cheers guys, rad help! |
Haaaaaaaaaaaaaallelouya :) For five days I searched why my grunt-contrib-watch exited silently... By reading this topic, I updated NodeJs to 0.10.21 and the whole works with OSX 10.9. Thanks ! |
Awesome Possums! I was getting "Bus Error 10" on every file save, Upgraded from v0.10.20 on Mavericks & Wahla I can use my Grunt file again. Thanks for the help! |
Upgrade to 0.10.22 also works. |
0.10.22 works here too |
Is it possible that I'm still having this issue using the following versions?
|
@pedrombafonso Try downgrading to node |
Happening anyway. :s |
@pedrombafonso please provide the error log with the |
|
@pedrombafonso Is that with node |
@shama @vladikoff you were right. I was configuring the version on nvm, but I had another node installation in the path. it's solved. thanks. |
This was causing me a headache for a while, I was also using Node 0.10.18 with OSX 10.9 Mavericks. I managed to get it working with a newer version of Node, I am now on Node 0.10.25, I updated the node version using Node Version Manager: https://github.com/creationix/nvm |
Same here! Best! |
Haha! Nice seeing a familiar face here, @TJXStyles! Great forum -- doing a |
Node update .. thanks |
A workmate is seeing this issue on 0.10.28 so we upgraded to 0.10.29 and experience the same issue. OSX 10.9.1 |
Upgrading node solved the problem for me. In order to upgrade it I followed this tutorial http://davidwalsh.name/upgrade-nodejs |
Hi, I realize I'm running a developer preview of OS X but before I roll back to 10.8 I wanted to see if there's a fix to the following error. When a change is detected, the watch task breaks my 'grunt server' with the following:
OS X 10.9 DP7
Node 0.10.18
Grunt 0.4.1
Generator-webapp 0.4.2 (didn't change a line in the code so gruntfile etc. are all the defaults)
The text was updated successfully, but these errors were encountered: