Michal Nazarewicz

I took a quick look and it appears vterm doesn’t support face remapping (mind you, I haven’t looked at vterm’s code so I could be wrong).

It looks like declaring `custom-heap` feature fixes this issue. As far as I understand, with the feature defined, Solana doesn’t define a global allocator and if the smart contract doesn’t...

Looks like the allocator is set at https://github.com/solana-labs/solana/blob/a2d2eb3ba80824f55c9cbd267ab881a285ca324a/programs/bpf_loader/src/lib.rs#L256 and it gets the heap size from the vm configuration. On first glance it seems that the global allocator defined by `#[entrypoint]`...

> i think the issue with the default runtime allocator is that it's not a bump allocator and hence uses more compute If BpfAllocator is the default runtime allocator, than...

> could fetch limit from instruction introspection during bump alloc initialization, would be a relatively quick fix without addition of a new syscall This requires access to instruction sysvar AccountInfo....

Also note that `solana_program::entrypoint::deserialize` and `load_instruction_at_checked` perform allocations. Current BumpAllocator implementation allocates from the end of the heap (which is correct and faster for bump allocators) which means the allocator...

Done. Ironically enough, if it was in FAQ it probably wouldn’t have helped me either, since it’s only now that I discovered that FAQ exists. Though maybe it would be...

On Wed, 25 Jun 2025 at 13:00, Evgeny Stambulchik ***@***.***> wrote: > Well, FAQ isn't a list of known bugs. And even when it talks about a bug, this is...

Friendly ping.

@jackcmay, what’s the status of this? [The schedule](https://github.com/anza-xyz/agave/wiki/Feature-Gate-Activation-Schedule#features-are-blocked) says this is blocked on user demand. Henceforth, I do have demand for it as I’m trying to implement an on-chain light...