Delphi Rio 10.3.3 crashes on big multiline constants.

[vhanla 2]

https://quality.embarcadero.com/browse/RSP-27564

 

I reported that issue, hopefully you can help me to avoid this issue.

 

I'm including constants of large strings as it will be embedded in the executable, each constant has many characters, because they contain compressed javascript libraries, previous Delphi versions didn't have any issue with these, maybe is because of the recent changes to the variable declaration, I'm not sure, but this one just hangs and closes without any warning.

 

Here I include a demo that crashes after opening it.

CrashIDE.zip

Edited February 3, 2020 by vhanla

[vhanla 2]

As I noticed, in one constant, if it surpasses 1255 lines, that error happens, maybe it is different on other machines.

[vhanla 2]

Maybe they reduced the maximum lines for constants in multiline appends, so the current workaround was to reduce them by splitting into another constant, using another text editor of course.

[Dave Nottage 492]

You should consider compiling the text into the app and loading it as a resource. See here:

 

https://stackoverflow.com/a/8943364/3164070

[vhanla 2]

Thank you, that would be ideal, though I just wanted to avoid that.

So it seems that a registry tweak fixes that.
 

Quote

The IDE uses the following value as each parser-thread's reserved-stack. (The max size of the thread's stack.)

Key Name: HKEY_CURRENT_USER\Software\Embarcadero\BDS\20.0\Globals
Name: ReservedStackSize
Type: REG_DWORD
The value entered is used as the reserved-stack-size for each parser thread. If the registry key doesn't exist, the default value is $600000 (6M) bytes.

That fixed it.

 

https://quality.embarcadero.com/browse/RSP-22274

[Sherlock 627]

Since nothing is as volatile as a web thing, consider keeping that in a text file and load it once your application has started. This gives you the added benefit of being able to change this HTML-File without the need for an update.

[Lars Fosdal 1732]

The process of making a change to the example file in the QP case would be painstaking and error-prone.

I'd compress the original file, add it as a resource, and decompress in memory.

No worries about encoding, quoting, and such.

 

[David Heffernan 2300]

Certainly I'd do all the work to prepare the resource from the source file as a pre build step, properly automated. 

 

I'd question the choice to use compression. What is the point of that? 

[Lars Fosdal 1732]

Just now, David Heffernan said:

Certainly I'd do all the work to prepare the resource from the source file as a pre build step, properly automated. 

 

I'd question the choice to use compression. What is the point of that? 

Integrity control. 

[David Heffernan 2300]

31 minutes ago, Lars Fosdal said:

Integrity control. 

I don't understand that. 

[Martin Wienold 35]

6 hours ago, Lars Fosdal said:

Integrity control. 

Sign your file.