-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
SourceMapProxy::lookup_char_pos causes out of bounds memory access #7238
Comments
Note I could observe this only on aarch64 machines so far (m1 / aarch64 linux) but x86_64 passes. Possibly another case of #5406. |
Actually this seems like #6852. |
This comment was marked as off-topic.
This comment was marked as off-topic.
next.js issue is not relevant here since next.js is not using the corresponding swc_core yet. |
**Description:** Maybe fix? #7238 wasmerio/wasmer#3764 (comment)
**Description:** Attempt to workaround #7238. Originally I thought this is related with oom or memory layout, then realized actual deserialization error occurs in weird position - it tries to deserialize BytePos (which is obvious type) and it fails. It made me think maybe a property next to the struct layout have some unexpected behavior, notably Arc<String>. PR applies same workaround as Atom does, and it seems to at least pass swc-coverage-instrument's usecases. May need bit more verification with other plugins to see if we can call this out as reliable workaround.
**Description:** Second attempt to enable bytecheck. This PR does not have versioned struct yet, just enabling bytecheck wherever possible. Also, it is for the ast only yet, so transform metadata and others might need this later. PR seems to be passing all the ci, but as we've experienced before, there might be some unexpected outcomes with the release. Maybe better to hold this until clear #7238, then land as a separate release.
Tentatively closing as we applied workaround. |
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Describe the bug
Input code
No response
Config
No response
Playground link
No response
Expected behavior
should not oob
Actual behavior
No response
Version
latest
Additional context
No response
The text was updated successfully, but these errors were encountered: