Node Bus Error
Contents |
Sign in Pricing Blog Support Search GitHub This repository Watch 122 Star 3,162 Fork 431 sass/node-sass Code Issues 66 what is bus error 10 Pull requests 21 Projects 1 Pulse Graphs New issue Bus error
Webpack Bus Error
with node-sass@3.0.0 #946 Closed josip opened this Issue May 11, 2015 · 7 comments Projects None bus error 10 mac yet Labels Bug - Confirmed External - LibSass Milestone v3.1.0 Assignees No one assigned 2 participants josip commented May 11, 2015 I'm having bus error 10 gulp a problem compiling a couple of files with node-sass@3.0.0, the error I get doesn't seem very helpful unfortunately: $ node-sass src/scss/app.scss [1] 65321 bus error node-sass src/scss/app.scss I can compile the same file with both and node-sass@2.x and latest sassc. The root of the problem seems to be this @import statement: @import '../../node_modules/x/vendor/bootstrap/bootstrap'; (Bootstrap) Using
Grunt Sass Bus Error 10
node 0.10.32 on OS X 10.10.4. xzyfer commented May 11, 2015 Hi @josip, this issue has come a few times but noone has given up a workable test cases. This is issue is very rare and hard to reproduce. If you are able to strip down your code to and make it available to us that would be great. Unfortunately we cannot fix this issue if we cannot reproduce it. xzyfer added Awaiting Response Bug - Maybe labels May 11, 2015 josip commented May 11, 2015 @xzyfer http://cl.ly/3U0x0F1b0C1P if you run test.sh you should see it fail with node-sass. For comparison, this is what I get: $ ./test.sh node-sass 3.0.0 (Wrapper) [JavaScript] libsass 3.2.2 (Sass Compiler) [C/C++] ./test.sh: line 5: 68412 Bus error: 10 node-sass src/scss/app.scss ================= sassc: 3.1.0 libsass: 3.0.3 sass2scss: 1.0.3 /*! normalize.css v3.0.2 | MIT License | git.io/normalize */ xzyfer commented May 11, 2015 Is the issue present with a more recent scss? brew update && brew install sassc
Sign in Pricing Blog Support Search GitHub This repository Watch 112 Star 1,497 Fork 118 at-import/Singularity Code Issues bus error (core dumped) 17 Pull requests 1 Projects 0 Wiki Pulse Graphs New node-sass issue Node-sass failing with Bus error 10 #211 Closed Nooshu opened this Issue May 21, 2015 ·
Gulp-sass
3 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 4 participants Nooshu commented May 21, 2015 Hello, https://github.com/sass/node-sass/issues/946 I've just run into an issue that kills node-sass. Adding these lines together ends in node-sass giving a 'bus error'. When each line is added on its own it doesn't crash. @import '../../../../../../bower_components/singularity/stylesheets/singularitygs'; @include sgs-change('debug', true); @include background-grid(); It gives the following console error: node-sass 3.1.2 (Wrapper) [JavaScript] libsass 3.2.4 (Sass Compiler) [C/C++] Loading https://github.com/at-import/Singularity/issues/211 "sass.js" tasks...OK + sass Running "sass" task Running "sass:dist" (sass) task Verifying property sass.dist exists in config...OK Files: build/src/etc/designs/project/sass/test.scss -> build/dist/etc/designs/project/css/test.css Options: precision=10, sourceMap, outputStyle="expanded" [1] 69434 bus error grunt sass --v I've also attached the log from OSX available here It only seems to have started happening in the last week or so, so i'm not sure what has changed. Hopefully that helps, it was a bit of a pain to debug! Note: It's also worth noting that this only crashes node-sass on OSX. Running it inside Vagrant using Ubuntu 14.04 it runs fine. Thanks. the-Dean commented Jul 10, 2015 I just posted the same issue, but with one difference, its using these two lines together that causes the issue @include sgs-change('debug', true); @include background-grid(); Did you find a solution for it? humanaut commented Sep 1, 2015 I just encountered this issue also. digitaldonkey commented Oct 1, 2015 Any solution? 58bits referenced this issue Nov 29, 2015 Closed Li
Sign in Pricing Blog Support Search GitHub This repository Watch 36 Star 961 Fork 232 dlmanning/gulp-sass Code Issues 30 Pull requests 3 Projects 0 Wiki Pulse Graphs New issue Bus error (core https://github.com/dlmanning/gulp-sass/issues/401 dumped) #401 Closed eyakcn opened this Issue Nov 30, 2015 · 17 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 6 participants eyakcn commented Nov http://stackoverflow.com/questions/20887400/gruntjs-bus-error-grunt-watch 30, 2015 I was running a Jenkins in docker container, and when the job execute gulp-sass task, it fails. The error message: Bus error (core dumped) The gulp file options: var sassOptions = { bus error style: 'expanded' }; Dependencies: gulp-sass: v2.0.4 guilp: v3.9.0 npm: v3.3.12 node: v5.1.0 Compass 1.0.3 (Polaris) Collaborator xzyfer commented Nov 30, 2015 Please provide the smallest possible Sass file that still causes this issue. Do not include frameworks. eyakcn commented Nov 30, 2015 It has nothing to do with the sass file, because I can run the gulp task of sass only my local machine without any problem. I bus error 10 think maybe it's due to "running gulp sass task inside a docker container" Collaborator xzyfer commented Nov 30, 2015 Bus error is an issue with LibSass resulting from your Sass. It's like due to an invalid memory access which is why it doesn't happen on your host system. Please provide the smallest possible Sass file that still causes this issue. Do not include frameworks. eyakcn commented Nov 30, 2015 Thank you for your reply. So how can I get more debug info about this problem? Any suggestions? Collaborator xzyfer commented Nov 30, 2015 The only way to debug this kind of issue is to comment out sections of code until you the error no longer occurs. When the error stops the problematic code was in code commented out. Uncomment that and comment out other code. Keep doing this until you end up with the smallest amount of code required to make the bug happen. eyakcn commented Nov 30, 2015 Wow... So currently there are no other people report this problem? Have you tried to run some gulp sass task inside a docker container? Maybe you can reproduce the same error, too. My docker container was build on top of ubuntu:14.04 Collaborator xzyfer comme
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up GruntJS “bus error grunt watch” up vote 5 down vote favorite I'm having an error with GruntJS when I try to run a grunt watch. It works fine, until there is a change in the file it is watching, then, it looks something like this: Running "watch" task Waiting...[1] 2464 bus error grunt watch The number 2464 changes. It seems to be the port that grunt is watching on? But, I'm not sure. Here is my Gruntfile: module.exports = function (grunt) { "use strict"; grunt.initConfig({ pkg: grunt.file.readJSON('package.json'), sass: { dist: { options: { style: 'compact' }, files: { 'css/style.css': 'sass/style.scss', } } }, watch: { files: 'sass/style.scss', tasks: ['sass'] } }); grunt.loadNpmTasks('grunt-contrib-sass'); grunt.loadNpmTasks('grunt-contrib-watch'); grunt.registerTask('default', ['sass']); }; Thanks in advance for all the help! command-line terminal sass gruntjs watch share|improve this question edited Jan 3 '14 at 8:13 Anzeo 10.8k44572 asked Jan 2 '14 at 16:37 xanesis4 116414 add a comment| 2 Answers 2 active oldest votes up vote 24 down vote accepted Do you use Osx maverick? checkout this: https://github.com/gruntjs/grunt-contrib-watch/issues/204 You need to upgrade node.js to 0.10.22 version: # Check your version of Node.js. v0.10.20 will still be broken node –v # clean your node cache sudo npm cache clean –f # install node binary manager ’n’ sudo npm install -g n # use said ’n’ manager