Skip to content

Conversation

mattsse
Copy link
Member

@mattsse mattsse commented Jun 13, 2025

we're holding the lock for the entire serialize call which is more expensive than cloning the data first, so we should clone so that we can drop the readlock immediately.

if this is serialized into a file directly via bufwriter this could cause issues

@mattsse mattsse requested review from DaniPopes and klkvr as code owners June 13, 2025 11:39
@onbjerg
Copy link
Contributor

onbjerg commented Jun 13, 2025

Ref foundry-rs/foundry#10452, possible solution

@mattsse mattsse merged commit 5453add into main Jun 13, 2025
13 of 15 checks passed
@mattsse mattsse deleted the matt/clone-for-serialize branch June 13, 2025 11:51
onbjerg added a commit to ithacaxyz/relay that referenced this pull request Jun 13, 2025
Fixes a flaky tx service test and adds `--no-storage-caching` which
temporarily solves the deadlock issue when fetching storage slots,
closing #792. This might be the same issue as
foundry-rs/foundry#10452 and could potentially
be solved when foundry-rs/foundry-fork-db#51
lands in Foundry
yongkangc pushed a commit to ithacaxyz/relay that referenced this pull request Aug 5, 2025
Fixes a flaky tx service test and adds `--no-storage-caching` which
temporarily solves the deadlock issue when fetching storage slots,
closing #792. This might be the same issue as
foundry-rs/foundry#10452 and could potentially
be solved when foundry-rs/foundry-fork-db#51
lands in Foundry
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants