David Heffernan

I quoted it in my previous comment. You might want to read it for yourself.

You don't need to know the size of anything to persist properties. The way to do that is to use the streaming framework. There are many example codes on the web. You are probably making a mistake in believing that you need to copy a block of memory. That's not how to do persistence of complex structures.

This is very complex. The answer you link to is the size when serialized. But that bears no real relation to the memory used by the class at runtime. Also there are the system resources that are used. The real question though is what you are planning to use this value for. Knowing that would allow us to understand better how you might solve this.

This is what was stated, @FPiette. What makes you think that there is a large amount of existing Delphi code.

That is beside the point of this topic. Remember what the OP has actually asked.

What the OP is asking for doesn't seem to have any requirement for server side code. Remember that we aren't talking about your requirements, we're talking about those of the OP.

And you don't think that maybe, just maybe, Delphi isn't the best tool for this?

You don't do that with Delphi is the simple answer.

a is for argument

We still have basically no idea what you are asking.

Generally it's wise to try not to do this.

There are countless ways in which Delphi code may be involved in web development. If you want anybody to spend their time helping you I suggest that you spend more of your time thinking about your problem, and specifying in more detail what specifically you need help with.

No

This has been answered above. It's the use of an intermediate string variable that holds the entire text which is then saved. And strings have 32 bit length. I'm not sure what @emailx45 is getting at but the problem you face is not due to a shortage of memory or address space. It's just that the string length is stored in a 32 variable. And a string is used by SaveToFile to save the text. FWIW, it seems wasteful to me to make an in memory copy of GBs of text just to save it. I'd be looking for a writer based approach. Just not using the raw RTL classes because of their dire performance.

What exactly is your rationale for wanting to use multiple engines? Why is it not possible to do this with a single engine?

You can't have generic helpers.

You don't need the if. You know that sList is not nil. Also, Free already includes a nil check. Also, there is the <> operator for not equals.

Is your executable compiled with the overflow checks compiler option enabled?

In what way? Can you be more specific. As for the main problem, I'm not surprised. I'd expect that you'd be better off using a stream writer to write such a huge collection to a stream. I'd submit a bug report to QP, in case on doesn't already exist, and then write some helper code to workaround the issue.

Maybe, but I'm still using XE7 which is why my own code doesn't use the RTL string helper.

https://quality.embarcadero.com/browse/RSP-10041 https://quality.embarcadero.com/browse/RSP-11302 Here are a couple of examples, but there are more.

Good point. But I'm using XE7 and the string helper has many many bugs, including I believe in one of the split or join functions. Plus, my version minimise heap allocation.

I mean. I'd start by using TRegistry. And I'd write the code myself rather than hacking at scraps found from the web.

I'm sure you will be able to debug it. Good luck.

Best to be clear on what you are doing here. The code seems to assume ANSI. Again are you using ANSI text?