Closed Bug 462412 Opened 16 years ago Closed 15 years ago

API for destroying fragments

Categories

(Tamarin Graveyard :: Baseline JIT (CodegenLIR), enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: dmandelin, Assigned: dmandelin)

References

Details

Attachments

(1 file)

In the regex world, memory management of fragments is relatively simple, because they belong to individual JSRegExp objects, so I'd like to be able to just delete the owned fragments when the regex is gc'd. But there's currently no API in Fragmento for doing this. There is an alternative of nuking all the fragments when gc occurs and rematerializing when needed, but I like this way better as the perf should be better and, more importantly, it seems more bug-avoidant.
Blocks: 461050
Attached patch PatchSplinter Review
Assignee: nobody → dmandelin
Status: NEW → ASSIGNED
Attachment #345822 - Flags: review?(gal)
Comment on attachment 345822 [details] [diff] [review] Patch David, is it safe to destroy fragments like that? What about the lirbuf?
Attachment #345822 - Flags: review?(gal) → review?(danderson)
Comment on attachment 345822 [details] [diff] [review] Patch There wasn't such a function before because lirbuffers could be shared across unrelated fragments. Even if you don't cause that to happen, having the API call sort of exposes the dependency problem. I'd put a big warning that the fragment's lirbuf can be shared and it's the user's responsibility to track dependencies.
Attachment #345822 - Flags: review?(danderson) → review+
looks like this has been done for a long time now. reopen if it needs to track a more specific problem.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: