This is clutching at straws, but is it maybe to do with the size of Meteor’s bundler cache? There have been reports over the years of this causing longer build times as it grows. In your application root:
rm -rf .meteor/local/bundler-cache
It may also be worth removing Meteor’s package cache from your home directory:
rm -rf ~/.meteor/packages/meteor-tool
The only reason I suggest this is that I’ve seen issues on the forums to do with open file limits on Macs (which could potentially affect Linux too). I don’t have a Mac and have not experienced this on Linux, so feel free to ignore me!
@robfallows Thanks very much for the suggestion. I did remove both of those files. Both were huge, especially bundler-cache. And then I reinstalled meteor. I managed to develop for almost an hour before I had a seg fault, which is certainly an improvement.
Any other ideas, robfallows? Or anyone else? I’m very motivated to help solve this one, b/c it’s a royal pain.
I have been getting the segmentation fault on startup ‘meteor -s settings.json’ for over a week. I spun up a Vagrant box to run the same code and things work good in there.
The machine that gets the faults is a Macbook Pro running 10.12.4. I was in the process of upgrading an old project Meteor 1.2 -> 1.3 -> 1.4 when the segmentation faults happened. I finished the upgrade on Vagrant. The app is currently at 1.4.4.2. I removed the bundler-cache and have reinstalled Meteor several times. Even ‘meteor create test-app’ gives the fault error.
With Meteor 1.5, this issue is 90 to 95% reduced for me. I’ve maybe 3 seg faults in 4 days of development. Not completely gone and I would still love to know if there’s anything I can do on my end to protect against it, but this improvement is a huge relief. I was having around 10 faults a day before.
Wow, the trashcan is so nice; never heard of anyone actually having one, much less for dev work. And 64g of ram? Insane. I found my 13" Macbook, even with 16g of ram, always seems starved for resources when I have too many tabs and windows opened and a lot going on.
I also do music production, so the 64GB is pretty important. As a nice side benefit, it makes for a pretty powerful dev machine too! If I were just doing dev work, I’d probably go for 32GB. I think 16GB these days is just not enough for pro work.
Tried about everything (downgrading node to 4.8.2, removing cache, making sure enough cpu is available, removing white lines in package.json), still receiving this error every 3-4 refreshes.
And 64g of ram? Insane. I found my 13" Macbook, even with 16g of ram, always seems starved for resources when I have too many tabs and windows opened and a lot going on.
As a nice side benefit, it makes for a pretty powerful dev machine too! If I were just doing dev work, I’d probably go for 32GB. I think 16GB these days is just not enough for pro work.