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

feat(span): fix memory leak by implementing inlineable string for oxc_allocator #2294

Merged

Conversation

Boshen
Copy link
Member

@Boshen Boshen commented Feb 4, 2024

closes #1803

This string is currently unsafe, but I want to get miri working before introducing more changes.

I want to make a progress from memory leak to unsafe then to safety. It's harder to do the steps in one go.

Copy link

netlify bot commented Feb 4, 2024

Deploy Preview for oxc canceled.

Name Link
🔨 Latest commit 9099d5c
🔍 Latest deploy log https://app.netlify.com/sites/oxc/deploys/65bf6a73ee90380008388d13

Copy link
Member Author

Boshen commented Feb 4, 2024

Current dependencies on/for this PR:

This stack of pull requests is managed by Graphite.

@github-actions github-actions bot added the A-semantic Area - Semantic label Feb 4, 2024
@Boshen
Copy link
Member Author

Boshen commented Feb 4, 2024

Copy link

codspeed-hq bot commented Feb 4, 2024

CodSpeed Performance Report

Merging #2294 will degrade performances by 7.7%

Comparing 02-04-feat_span_implement_inlineable_string_oxc_allocator (9099d5c) with main (1822cfe)

Summary

❌ 3 (👁 3) regressions
✅ 14 untouched benchmarks

Benchmarks breakdown

Benchmark main 02-04-feat_span_implement_inlineable_string_oxc_allocator Change
👁 semantic[pdf.mjs] 139.3 ms 150.9 ms -7.7%
👁 semantic[antd.js] 777.4 ms 811.9 ms -4.24%
👁 semantic[checker.ts] 607.6 ms 634.4 ms -4.23%

@Boshen Boshen force-pushed the 02-04-feat_span_implement_inlineable_string_oxc_allocator branch from 8d4b0ef to ba1e860 Compare February 4, 2024 10:38
…_allocator

closes #1803

This `String` is currently unsafe, but I won't to get miri working
before introducing more changes.
@Boshen Boshen force-pushed the 02-04-feat_span_implement_inlineable_string_oxc_allocator branch from ba1e860 to 9099d5c Compare February 4, 2024 10:44
@Boshen Boshen merged commit 6002560 into main Feb 4, 2024
26 checks passed
@Boshen Boshen deleted the 02-04-feat_span_implement_inlineable_string_oxc_allocator branch February 4, 2024 11:28
@Boshen Boshen mentioned this pull request Feb 4, 2024
IWANABETHATGUY pushed a commit to IWANABETHATGUY/oxc that referenced this pull request May 29, 2024
…_allocator (oxc-project#2294)

closes oxc-project#1803

This string is currently unsafe, but I want to get miri working before
introducing more changes.

I want to make a progress from memory leak to unsafe then to safety.
It's harder to do the steps in one go.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-semantic Area - Semantic
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Memory leak in arena with Atoms
1 participant