Having exit code 134 on Ruby 2.4.1 & Rails 4.2.0 enviroment

We are building our app using Ruby 4.2.1 and Rails 4.2.0.
After we upgraded ruby from 2.2.1 to 4.2.1, I started having exit code 134 error on Circle CI.
Strangely, when I had the error, if I run the same spec on my local environment for the exact same brunch, it passes all the test always.

Mostly, Error message is kind like this

*** Error in `/opt/circleci/ruby/ruby-2.4.1/bin/ruby’: free(): invalid pointer: 0x00007ff9dae68450 ***

Currently we are rebuilding the same brunch and it passes if we rebuild it over and over
(Actually, I rebuild the same brunch 4 times today to get passed.)

Do any of you guys having the same kind of problems?
Could you give me some advice?

When you rebuild without cache, does the error go away? If so, there might be some corruption. We can clear it out for you and start fresh.

Thanks. Let me try it. We are just pushing rebuild with crossing our fingers always. If we could pass the test by your way, I’ll let you know.

If running without cache does the trick, send us an email to support@circleci.com with the project URL so we can flush the cache for you.