-
Notifications
You must be signed in to change notification settings - Fork 208
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
XS instrumentation: upstream? #3139
Labels
Comments
#3262 is more manual maintenance |
This was referenced Aug 5, 2021
Aug 5, I wrote: @warner replied:
So that's what I'll do... |
dckc
added a commit
that referenced
this issue
Aug 9, 2021
- xsnap-worker - get xsnap heap exhaustion crash fix - never mind meters beyond compute, allocate refs #3139
dckc
added a commit
that referenced
this issue
Aug 13, 2021
- xsnap -> xsnap-worker to distinguish cli app from long-running worker - get xsnap heap exhaustion crash fix - never mind meters beyond compute, allocate refs #3139
dckc
added a commit
that referenced
this issue
Aug 14, 2021
Moddable reworked the chunk allocator to always use a single memory block for chunk storage. The change is implemented in `xsnapPlatform.c`. The implementation uses `mmap`/`mprotect` (`VirtualAlloc` on Windows) to reserve and to commit memory pages. To get this fix, we add an `xsnap-native` submodule that replaces `xsnap.c` and friends. The submodule includes a few tweaks: https://github.com/agoric-labs/xsnap-pub/tree/endo-submodule fixes #3577 fixes #3139 , bringing us back to stock XS. fixes #2469 - Moddable reviewed the code well enough to substantially re-work it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the Problem Being Solved?
Integrating new XS code automatically (#2648) is infeasible since we switched over to our fork when we made some tweaks for instrumentation during testnet: agoric-labs/moddable#5
Description of the Design
Options include:
cc @warner @kriskowal @dtribble @phoddie @michaelfig
The text was updated successfully, but these errors were encountered: