Skip to content

Conversation

ahorek
Copy link
Contributor

@ahorek ahorek commented Oct 2, 2019

this attempts to fix a problem with thread safety, see #581 for more context

fixes #633 sass/sassc-ruby#133 sass/sassc-rails#122 sass/sassc-rails#58 #638 ...

there's a race condition between sassc_processor.rb and sassc_compressor.rb, both calls SassC::Engine with different functions.

WIP because it this depends on sass/sassc-ruby#162

1/ no more segfaults even with concurrency enabled
2/ sass gem has the same problem, but the gem is deprecated, so it can't be fixed
3/ https://github.com/sass/sassc-rails will require a similar change

@glebm
Copy link
Contributor

glebm commented Apr 19, 2020

sassc 2.3.0 has been released

@glebm
Copy link
Contributor

glebm commented May 3, 2020

@ahorek I think we'd also need to replace the dependency on sass with a dependency on sassc >= 2.3.0

This was referenced Jun 9, 2020
@schneems
Copy link
Member

is this ready to merge or still WIP?

@ahorek
Copy link
Contributor Author

ahorek commented Sep 25, 2020

well, since sassc 2.3 is out for 6 months, there's nothing else blocking this PR.

however, it's difficult to write a reliable test case for it. It would require concurrent access to sass template that includes url helpers.

sass/sassc-rails#148 might be an alternative, but I didn't test it by myself.

@ahorek
Copy link
Contributor Author

ahorek commented Dec 20, 2022

closing this, because it seems to be resolved by a slightly alternative approach #759 .... after 3 years, ouch... :-(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Segfault
3 participants