Skip to content

Remove CPU-native config#648

Merged
vinistock merged 2 commits intomainfrom
03-06-remove_cpu-native_config
Mar 6, 2026
Merged

Remove CPU-native config#648
vinistock merged 2 commits intomainfrom
03-06-remove_cpu-native_config

Conversation

@vinistock
Copy link
Copy Markdown
Member

@vinistock vinistock commented Mar 6, 2026

We not only continue to see the crashes in our memory leak check, but we are seeing the crash when running regular CI on Ubuntu and in projects adopting Rubydex.

I have one more hypothesis: maybe using native as the target CPU is creating some incompatibility between the Ubuntu environment where the gem gets pre-compiled and the one where it runs.

This PR is another attempt to fix this. It reverts the memleak changes and removes our target-cpu. We added the target-cpu for performance, but it makes no actual difference in our benchmarks.

@vinistock vinistock self-assigned this Mar 6, 2026
Copy link
Copy Markdown
Member Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@vinistock vinistock added the bugfix A change that fixes an existing bug label Mar 6, 2026 — with Graphite App
@vinistock vinistock marked this pull request as ready for review March 6, 2026 15:31
@vinistock vinistock requested a review from a team as a code owner March 6, 2026 15:31
@vinistock vinistock force-pushed the 03-06-remove_cpu-native_config branch from bc440f5 to c87d64f Compare March 6, 2026 15:33
Copy link
Copy Markdown
Contributor

@Morriar Morriar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤞

@vinistock vinistock merged commit a83970c into main Mar 6, 2026
26 of 27 checks passed
@vinistock vinistock deleted the 03-06-remove_cpu-native_config branch March 6, 2026 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugfix A change that fixes an existing bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants