node-sass 4.8.1 crashes with WebPack running parallel compilation

[horaceleung]

We have been using "node-sass": "^4.5.3" in our package.json for some time now and since yesterday, we have been getting an error when run 'npm start'. Error below:

node(7981,0x70000b18c000) malloc: *** error for object 0x1041ac8b0: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug

However when we downgrade and fix the version to 4.5.3, we do not get the error anymore. ( without ^ to "node-sass": "4.5.3") so I am certain it is an issue caused by the latest version, possibly 4.8.1 ?

Please advice on this.

• NPM version (5.7.1)
• Node version (v8.10.0)
• Node Process ({ http_parser: '2.7.0',
  node: '8.10.0',
  v8: '6.2.414.50',
  uv: '1.19.1',
  zlib: '1.2.11',
  ares: '1.10.1-DEV',
  modules: '57',
  nghttp2: '1.25.0',
  openssl: '1.0.2n',
  icu: '60.1',
  unicode: '10.0',
  cldr: '32.0',
  tz: '2017c' }
  )
• Node Platform (darwin):
• Node architecture (x64)
• node-sass version (node-sass 4.8.1 (Wrapper) [JavaScript]
  libsass 3.5.0 (Sass Compiler) [C/C++])
• npm node-sass versions ( node-sass@4.8.1 ):

[xzyfer]

Are you able to provide some same code that produces this error? We can't debug this if we cannot reproduce it.

…

On 12 Mar. 2018 7:46 pm, "Horace Leung" ***@***.***> wrote: We have been using "node-sass": "^4.5.3" in our package.json for some time now and since yesterday, we have been getting an error when run 'npm start'. Error below: *node(7981,0x70000b18c000) malloc: *** error for object 0x1041ac8b0: pointer being freed was not allocated *** set a breakpoint in malloc_error_break to debug* However when we downgrade and fix the version to 4.5.3, we do not get the error anymore. ( without ^ to "node-sass": "4.5.3") so I am certain it is an issue caused by the latest version, possibly 4.8.1 ? Please advice on this. - NPM version (5.7.1) - Node version (v8.10.0) - Node Process ({ http_parser: '2.7.0', node: '8.10.0', v8: '6.2.414.50', uv: '1.19.1', zlib: '1.2.11', ares: '1.10.1-DEV', modules: '57', nghttp2: '1.25.0', openssl: '1.0.2n', icu: '60.1', unicode: '10.0', cldr: '32.0', tz: '2017c' } ) - Node Platform (darwin): - Node architecture (x64) - node-sass version (node-sass 4.8.1 (Wrapper) [JavaScript] libsass 3.5.0 (Sass Compiler) [C/C++]) - npm node-sass versions ( ***@***.*** ): — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2280>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAjZWIob0aF9Qtjl68j46HjQ1O7OWt3Dks5tdjYAgaJpZM4SmQE7> .

[horaceleung]

This is our config, the issue is with sass-loader is not functioning and crashes with the mentioned error. If we remove sass-loader { loader: 'sass-loader' }, the error goes away. However we found the root cause was with node-sass latest version.

[chrishyle]

We are also experiencing this with a similar setup (darwin, node 8.9.4, webpack/sass-loader). Issue Started with 4.8.1; 4.7.2 works fine.

I regrettably cannot provide code.

[xzyfer]

Unfortunately we don't work with webpack so this config does not help us debug the issue.

Are you able to track down the actual Sass code that results in this error i.e. the specific @import that if you comment it out the error goes away.

[horaceleung]

Unfortunately I also can't provide my code but not sure if I can say which exact line causing it but I think this is a "general/overall' issue. All I know is that I downgrade to previous version and everything works.

[xzyfer]

I am also unable to reproduce this running the sass-loader test suite.
I'll keep digging but without a way to reproduce this our hands are tied.

[xzyfer]

Can you both confirm the version of webpack, and sass-loader you're using with the following:

$ npm ls webpack sass-loader

[horaceleung]

sass-loader@6.0.7

[joernroeder]

same here after i've updated from 4.7.2 to 4.8.1

─ sass-loader@6.0.7
─ webpack@3.11.0

[xzyfer]

Are you able to create a reproducible test case you can share? Without
actual Sass code there is no progress to be made here unfortunately.

I am unable to reproduce this my own, or some open source projects using
sass-loader.

Please do not comment with "me too"s.

You can subscribe to updates with the subscribe button -->

[xzyfer]

If anyone has time to help us debug this in real time, please join us in Slack.
https://libsass-slack.herokuapp.com/

[xzyfer]

Update: I've be blindly trying random github repos that use sass-loader in order to reproduce the issue. I have managed to stumble across one. Debugging the issue now.