Project

General

Profile

Actions
Copy link

Bug #16765

closed

Crash when use sass image-url in email layout

Added by chellgouda (Mitchell Gould) about 5 years ago. Updated almost 5 years ago.

Status:
Closed
Assignee:
-
Target version:
-
ruby -v:
ruby 2.5.7p206 (2019-10-01 revision 67816) [x86_64-darwin18]
Backport:
2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
[ruby-core:97734]

Description

I have the following layout I use for my emails:

mailer.html.slim

doctype html
html
head
meta(charset='utf-8')
meta(http-equiv="Content-Type" content="text/html")

css:

Files

ruby_2020-04-06-170518_Mitchells-MacBook-Pro-3.crash (72.3 KB) ruby_2020-04-06-170518_Mitchells-MacBook-Pro-3.crash chellgouda (Mitchell Gould), 04/06/2020 09:36 PM
Actions
Copy link
 #1 [ruby-core:97735]

Updated by chellgouda (Mitchell Gould) about 5 years ago

doctype html
html
head
meta(charset='utf-8')
meta(http-equiv="Content-Type" content="text/html")

scss:
  .footer-box:after {
    content: '';
    width: 100%;
    height: 100%;
    opacity: 0.1;
    position: absolute;
    top: 0;
    left: 0;
    background: image-url( 'logo/gould_logo_black.png' ) no-repeat bottom 15% right -15%;
    background-size: 30%;
  }

This causes a crash

Using slim 4.0.1
Using slim-rails 3.2.0
Using sassc 2.2.1

Rails 5.2.4.2

Actions
Copy link
 #2 [ruby-core:97736]

Updated by jeremyevans0 (Jeremy Evans) about 5 years ago

  • Status changed from Open to Feedback

Unfortunately, the crash report does not provide the relevant debugging information:

Thread 22 Crashed:: thread_pool.rb*
0   libsystem_kernel.dylib        	0x00007fff6cd2c33a __pthread_kill + 10
1   libsystem_pthread.dylib       	0x00007fff6cde8e60 pthread_kill + 430
2   libsystem_c.dylib             	0x00007fff6ccb3808 abort + 120
3   libruby.2.5.dylib             	0x0000000106564939 die + 9
4   libruby.2.5.dylib             	0x0000000106564b74 rb_bug_context + 564
5   libruby.2.5.dylib             	0x0000000106659cf1 sigsegv + 81
6   libsystem_platform.dylib      	0x00007fff6cddd5fd _sigtramp + 29

It does appear to be a null pointer dereference:

Exception Type:        EXC_BAD_ACCESS (SIGABRT)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000

While there isn't much to go by, it seems likely to be a bug in sassc. There are other null pointer dereference bugs on their issue tracker already: https://github.com/sass/sassc-ruby/issues

Can you reproduce this issue without sassc?

Actions
Copy link
 #3

Updated by jeremyevans0 (Jeremy Evans) almost 5 years ago

  • Status changed from Feedback to Closed
Actions
Copy link

Also available in: Atom PDF

Like0
Like0Like0Like0