You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bump sprockets down to a 3. version (changing it to >3 and <4)
Bump sassc down to 2.0.0 or up to 2.4.0 (The bug persists through 2.4.0, it's not known if it persists further)
Adding the following to config/initializers/assets.rb or a more relevant assets.rb file:
# Bypass segfault in sassc 2.* + sprockets 4: https://github.com/rails/sprockets/issues/581#issuecomment-486984663
Rails.application.config.assets.configure do |env|
env.export_concurrent = false
end
Selected Remediation:
Given that we do not explicitly depend on sprockets or sassc in our Gemfile, I decided to go with remediation 3, and move up the list if that does not solve it.
Problems
Because this issue is intermittent, it is not guaranteed that any given remediation will actually have solved the problem until we fail to see it happen long-term
The text was updated successfully, but these errors were encountered:
Problem
There is currently an intermittent Segmentation Fault when running the build/test step
The output is roughly:
Cause
This is due to a concurrency race condition bug in the combination
sprockets-4.0.0
andsassc-2.2.1
, see the following issues for more information: sass/sassc-ruby#167, rails/sprockets#581, rails/sprockets#633, rails/sprockets#630Possible Remediations:
config/initializers/assets.rb
or a more relevant assets.rb file:Selected Remediation:
Given that we do not explicitly depend on
sprockets
orsassc
in our Gemfile, I decided to go with remediation 3, and move up the list if that does not solve it.Problems
Because this issue is intermittent, it is not guaranteed that any given remediation will actually have solved the problem until we fail to see it happen long-term
The text was updated successfully, but these errors were encountered: