The error came with 64 * 1024 btw, i just tried to lower the value to see when it starts to hang.
First i used the "out-of-the-box" PB4.0 Version.
When i realized this behaviour i tried with all the beta-libs installed.
It is still the same effect...
Do you see the "What happened ?" - Output no matter how big your fixed string is ?
This one works, if I put 16321 in there it hangs. Something isn't right, the docs say fixed strings are unlimited. Outside a procedure it seems to take anything without a problem, but inside - 16320 is it. (here, with 2g ram)
Update: Inside the procedure only has the problem if the variable is protected. Static, Shared and Global vars declared inside the proc don't seem affected.
with netmaestro code: 12224 works and 12225 doesn't work
512 MB RAM
PureBasic 5.73 | SpiderBasic 2.30 | Windows 10 Pro (x64) | Linux Mint 20.1 (x64)
Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.
No idea, but perhaps it's for the same reason that my program crashes with and invalid memory access while displaying status bar text using different strings when the following line is compiled in a totally different routine and location...
Globe\MessageBoxText = "File is not a Take Note 22 settings file. File Not Loaded"
And doesn't crash when it's commented out.
The structure and declaration are fine. Something to do with string allocation or housekeeping? This was originally a non-structure string that also caused the same behavior and the program doesn't crash on other strings in the same structure.