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

Ocaml disables finalisation functions after an exception occured in one finalisation function call. #4742

Closed
vicuna opened this issue Mar 11, 2009 · 2 comments
Assignees
Labels

Comments

@vicuna
Copy link

vicuna commented Mar 11, 2009

Original bug ID: 4742
Reporter: rose
Assigned to: @damiendoligez
Status: closed (set by @damiendoligez on 2010-05-12T14:34:32Z)
Resolution: fixed
Priority: normal
Severity: minor
Version: 3.10.2
Fixed in version: 3.12.0+dev
Category: ~DO NOT USE (was: OCaml general)
Monitored by: @glondu @yakobowski

Bug description

If one value has an attached finalisation function, which raises an exception,
the user has to supply a manual 'Gc.finalise_release ()' call to reactivate
further processing of finalisation functions. A suggestion for a solution is
supplied as comment in the uploaded Ocaml file.

File attachments

@vicuna
Copy link
Author

vicuna commented May 25, 2009

Comment author: @damiendoligez

Instead of the solution you propose, we probably will ignore exceptions raised from finalisation functions (just as we ignore the return values).

This probably won't be fixed before version 3.12.0.

@vicuna
Copy link
Author

vicuna commented Aug 5, 2009

Comment author: @damiendoligez

Note to self: don't ignore exceptions, it prevents people from interrupting the main program when the heap gets too large.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants