HTTPAPI crashes when the value of a node is very large. This is happening for me when trying to parse an XML where one or more of the nodes contains an image; such as a signature or some other graphic attachment.
What is specifically crashing is this:
a. Program: HTTPAPIR4
b. Library: LIBHTTP
c. Module: HTTPUTIL4
d. Procedure: xrealloc
a. Code crashing: Realloc size Ptr
error message: The length requested for storage allocation is out of range.”
Does anyone know of a solution for this? Is there a patch or newer version of HTTPAPI I need to be using?
HTTPAPI crashing. Error messge: ":” The length requested for storage allocation is out of range.”
-
Scott Klement
- Site Admin
- Posts: 899
- Joined: Sun Jul 04, 2021 5:12 am
Re: HTTPAPI crashing. Error messge: ":” The length requested for storage allocation is out of range.”
You haven't told me which version you're running, so it's hard to say if there's a newer one. If you go to https://www.scottklement.com/httpapi/ you can see what the most recent version number is. Nothing has been changed related to this in a very long time, though.
Are you using the XmlReturnPtr feature?
If you are using this and you haven't done something weird like disable teraspace support, it should be able to store up to 224 gb in an allocation. Is your document larger than 224 gb?
Can you send me an XML file that reproduces the problem?
Are you using the XmlReturnPtr feature?
If you are using this and you haven't done something weird like disable teraspace support, it should be able to store up to 224 gb in an allocation. Is your document larger than 224 gb?
Can you send me an XML file that reproduces the problem?