You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 1473 Reporter: administrator Status: closed Resolution: not a bug Priority: normal Severity: minor Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: chris quinn
Version: 3.06
OS:
Submission from: 212.42.169.63 (212.42.169.63)
it seems custom finalisation only happens during
a sweep of the major heap.
if this is so then surely alloc_custom must not
allocate from the minor heap?
i have observed custom blocks in the minor heap not
being finalised when they go 'out of scope' before
the next minor collection.
chris
The text was updated successfully, but these errors were encountered:
it seems custom finalisation only happens during
a sweep of the major heap.
Correct.
if this is so then surely alloc_custom must not
allocate from the minor heap?
If you look at the source of alloc_custom, you'll see that allocation
is performed in the minor heap only if there is no finalization
function in the custom_operations struct.
i have observed custom blocks in the minor heap not
being finalised when they go 'out of scope' before
the next minor collection.
There should never be a custom block with non-NULL finalizer in the
minor heap. If you've observed this, please give us more details so
that we can track this bug down.
Original bug ID: 1473
Reporter: administrator
Status: closed
Resolution: not a bug
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: chris quinn
Version: 3.06
OS:
Submission from: 212.42.169.63 (212.42.169.63)
it seems custom finalisation only happens during
a sweep of the major heap.
if this is so then surely alloc_custom must not
allocate from the minor heap?
i have observed custom blocks in the minor heap not
being finalised when they go 'out of scope' before
the next minor collection.
The text was updated successfully, but these errors were encountered: