Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Specific exception for "the server failed to allocate memory" #1772

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Closed

Comments

@openstreetmap-trac
Copy link

Reporter: Richard
[Submitted to the original trac issue database at 7.10am, Thursday, 30th April 2009]

It would be good if there were a specific exception for "failed to allocate memory", so that whichways could trap it. At present any failure in whichways tells the user to e-mail me, which is good for Potlatch bugs, but not so good when it's a generic server problem.

@openstreetmap-trac
Copy link
Author

Author: tom[at]compton.nu
[Added to the original trac issue at 11.07am, Thursday, 30th April 2009]

It's not really possible as there is not a single way in which memory allocation failures manifest themselves that can be trapped - it all depends where the failure happens as ruby, the ruby libxml bindings, libxml itself, the ruby postgres bindings, and the postgres client library itself will all behave differently.

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

No branches or pull requests

1 participant