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

avm2: Fix handling of default domain memory #12308

Merged
merged 2 commits into from
Jul 26, 2023

Conversation

Aaron1011
Copy link
Member

Whenever ApplicationDomain.domainMemory is set to null (which is the default value), domain memory opcodes read from use hidden ByteArray in the domain. This hidden bytearray object is re-used if ApplicationDomain.domainMemory is ever set back to null.

@sleepycatcoding
Copy link
Member

sleepycatcoding commented Jul 25, 2023

Fixes #11793 (very very slow), #10230, #9681, #11426, #11566

Progresses #11408, #12304

There are probably more issues, but I got tired of searching through them.

core/src/avm2/domain.rs Outdated Show resolved Hide resolved
core/src/avm2/domain.rs Outdated Show resolved Hide resolved
@Aaron1011 Aaron1011 force-pushed the default-domain-memory branch from d147ec6 to 6928d9e Compare July 26, 2023 17:41
@Aaron1011 Aaron1011 enabled auto-merge (rebase) July 26, 2023 18:11
@Aaron1011 Aaron1011 disabled auto-merge July 26, 2023 18:11
@Aaron1011 Aaron1011 enabled auto-merge (squash) July 26, 2023 18:11
Whenever `ApplicationDomain.domainMemory` is set to `null`
(which is the default value), domain memory opcodes read from
use hidden ByteArray in the domain. This hidden bytearray object is re-used
if `ApplicationDomain.domainMemory` is ever set back to `null`.
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