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.”
-
- Site Admin
- Posts: 903
- 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?
Re: HTTPAPI crashing. Error messge: ":” The length requested for storage allocation is out of range.”
I am running version 1.42.
The HTPPAPI is cashing because the value in one of the of the nodes/fields can sometimes be too large. When this happens, I can delete the node and the .xml process fine.
It is not crashing because the .xml file is too large, rather it crashes when a field/node has too much data.
I am attaching a screen shot of the error I am getting.
Does this have to do with the XmlReturnPtr feature you mentioned? How can I tell if we are using that?
Scott, I am trying to attach a .txt with just the node that is causing HTTPAPI to crash but it may be too big to attach at 20bKB. Is there another way to get it to you?
Thanks for your help!!
The HTPPAPI is cashing because the value in one of the of the nodes/fields can sometimes be too large. When this happens, I can delete the node and the .xml process fine.
It is not crashing because the .xml file is too large, rather it crashes when a field/node has too much data.
I am attaching a screen shot of the error I am getting.
Does this have to do with the XmlReturnPtr feature you mentioned? How can I tell if we are using that?
Scott, I am trying to attach a .txt with just the node that is causing HTTPAPI to crash but it may be too big to attach at 20bKB. Is there another way to get it to you?
Thanks for your help!!
- Attachments
-
- HTTPAPI Crashing in XREALLOC.jpg (148.22 KiB) Viewed 114 times
-
- Site Admin
- Posts: 903
- Joined: Sun Jul 04, 2021 5:12 am
Re: HTTPAPI crashing. Error messge: ":” The length requested for storage allocation is out of range.”
Did you code it? Are you calling the http_XmlReturnPtr() subprocedure?krkatz12 wrote: Fri Aug 08, 2025 5:26 pm Does this have to do with the XmlReturnPtr feature you mentioned? How can I tell if we are using that?
I'm not familiar with the abbreviation 'bKB', so I have no idea how big your file is. If you meant 20 KB... that really should be no problem for anything to handle. That's quite small. Perhaps you mean 20 GB?krkatz12 wrote: Fri Aug 08, 2025 5:26 pm Scott, I am trying to attach a .txt with just the node that is causing HTTPAPI to crash but it may be too big to attach at 20bKB. Is there another way to get it to you?
At any rate, you could put it on any of a zillion different cloud sites (Dropbox, Box.com, Google Drive, OneDrive, etc, etc) and send me a link.