Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segfault #638

Closed
firefart opened this issue Oct 15, 2019 · 2 comments
Closed

Segfault #638

firefart opened this issue Oct 15, 2019 · 2 comments

Comments

@firefart
Copy link

firefart commented Oct 15, 2019

After upgrading to sprockets 4 I get the following segfault when trying to recompile the assets. Maybe it's related to #633 ?

The image is built using docker and the latest ruby:alpine image. On another project this runs just without issues so it must be something special here

The manifest.js is just the default one:

//= link_tree ../images
//= link_directory ../javascripts .js
//= link_directory ../stylesheets .css

Full output: https://pastebin.com/2m0z9aXi

@firefart
Copy link
Author

@schneems I can not provide you a sample app sorry, but it looks like there is a null pointer reference somewhere in the code. Is there perhaps a way to enable debug logging in sprockets to see on which file the error happens?

@schneems
Copy link
Member

Hello! Thanks for opening up an issue. In order to move forwards with this issue I'll need an example app that reproduce the behavior (https://www.codetriage.com/example_app).

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

No branches or pull requests

2 participants