Bus error in OS X 10.9

[oskarrough]

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:

Running "watch" task
Waiting...Bus error: 10

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)

[shama]

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.

[spacenick]

Got the same issue; OS X 10.8.5

Running "watch" task
Bus error: 10

[shama]

@spacenick Oh really? Which version of node.js?

[spacenick]

Oops yea sorry,

node v0.10.18
grunt-cli v0.1.9
grunt v0.4.1

[shama]

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

[spacenick]

Thanks @shama

[varju]

@spacenick Thanks; I assumed this was a 10.9 issue. Downgrading to node 0.10.17 fixed this for me.

[neekey]

Same issue with OSX 10.9, simple watch some .scss files and to compile them with grunt-contrib-compass but once file change is detected, it just crashed down:

$ grunt watch
Running "watch" task
Waiting...OK
>> File "src/common/style/_common.scss" changed.

Bus error: 10

OSX DP5
Node: v0.10.20
Grunt: 0.4.1

[neekey]

Thank you @varju, fix this problem downgrading to node 0.10.17

[aaronk6]

Thanks, @varju. Downgrading to 0.10.17 fixed it for me, too.

Here's how you downgrade to node 0.10.17 using homebrew:

cd $(brew --prefix)
brew update
git checkout f7bbdcc /usr/local/Library/Formula/node.rb
brew unlink node
brew install node

You can list all available node versions using brew versions node.

[davidkaneda]

Should this still be open? I feel like 10.9/Node 10.2 should be supported... Just not possible?

[shama]

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.

[kylebuch8]

After upgrading to OSX 10.9 I installed Node v0.10.21 and things started working again for me.

[andyscott]

After my initial OSX upgrade to 10.9, it failed. brew upgrade fixed everything for me.

[jasford]

I also just installed Mavericks, which caused this error to start happening for me. Upgrading Node to v0.10.21 resolved the issue.

[adambom]

Same as @jasford. Upgraded to 0.10.21 and it works again

[davidkaneda]

Same here, just upgraded :)

On Oct 22, 2013, at 4:06 PM, Adam Savitzky notifications@github.com wrote:

Same as @jasford. Upgraded to 0.10.21 and it works again

—
Reply to this email directly or view it on GitHub.

[varju]

0.10.21 looks good to me too.

[shama]

Thank you everyone! Closing with the recommendation of upgrading node to 0.10.21.

[andyscott]

The fact that there was so much activity here for the OSX upgrade makes me glad that I chose grunt as my build tool!

[davidkaneda]

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:

The fact that there was so much activity here for the OSX upgrade makes me glad that I chose grunt as my build tool!

—
Reply to this email directly or view it on GitHub.

[pyronaur]

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 :)

[ivan-demchenko]

I had the same error. Updated node from v0.10.20 to v0.10.21 via brew and the error has gone :) OSX 10.9

[bnoah-jh]

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:

curl https://raw.github.com/creationix/nvm/master/install.sh | sh

[mcranston18]

Upgrading to node v0.10.21 does the trick

[danielfilho]

Just updated to node v.0.10.21 and it works now. Thanks for reporting @mcranston18 :D

[caiogondim]

Working flawlessly now. Thanks guys.

[steveperrycreative]

Upgrading Node, via Brew, to 0.10.21 fixed this issue for me. OSX 10.9.

[gabeidx]

Yep, node v0.10.21 fixes it.

[phatshambler]

Same here, thanks!

[adamcbrewer]

Cheers guys, rad help!

[mica16]

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 !

[gfargo]

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!

[me97esn]

Upgrade to 0.10.22 also works.

[izidorome]

0.10.22 works here too

[pedrombafonso]

Is it possible that I'm still having this issue using the following versions?

• OSX 10.9.1
• node.js 0.10.26
• grunt-cli v0.1.13
• grunt v0.4.2

[shama]

@pedrombafonso Try downgrading to node 0.10.25 and see if it goes away. If so, it might be a regression.

[pedrombafonso]

Running "watch" task
Waiting...Bus error: 10

Happening anyway. :s

[vladikoff]

@pedrombafonso please provide the error log with the --verbose flag

[pedrombafonso]

Running "watch" task
Waiting...Verifying property watch exists in config...OK
Verifying property watch.js.files exists in config...OK
Verifying property watch.jstest.files exists in config...OK
Verifying property watch.gruntfile.files exists in config...OK
Verifying property watch.styles.files exists in config...OK
Verifying property watch.livereload.files exists in config...OK
Live reload server started on port: 35729
Watching app/scripts/demo-embers-fire.js for changes.
Watching app/scripts/demo-embers-init.js for changes.
Watching app/scripts/main.js for changes.
Watching test/spec/test.js for changes.
Watching Gruntfile.js for changes.
Watching .git for changes.
Watching .tmp for changes.
Watching app for changes.
Watching dist for changes.
Watching node_modules for changes.
Watching test for changes.
Watching app/styles/main.css for changes.
Watching app/404.html for changes.
Watching app/bower_components for changes.
Watching app/images for changes.
Watching app/scripts for changes.
Watching app/styles for changes.
Watching app/index.html for changes.
Watching .tmp/styles/main.css for changes.
Watching app/images/embers-thumbnail.jpg for changes.
Watching app/images/embers_background.jpg for changes.
Watching app/images/fire-embers-logo-h.png for changes.
Bus error: 10

[shama]

@pedrombafonso Is that with node 0.10.25? node -v to be sure as it should be fixed.

[pedrombafonso]

@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.

[TJXStyles]

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

[pedrombafonso]

Same here! Best!

[hellobrian]

Haha! Nice seeing a familiar face here, @TJXStyles!

Great forum -- doing a brew upgrade to node 0.10.26 got my grunt server and watch tasks to work with Ember App Kit. Thanks!

[ghost]

Node update .. thanks

[niallobrien]

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
Any suggestions?

[juanrules]

Upgrading node solved the problem for me. In order to upgrade it I followed this tutorial http://davidwalsh.name/upgrade-nodejs