Catastrophic Failure

The forum for ZeosLib 7.2 Report problems. Ask for help, post proposals for the new version and Zeoslib 7.2 features here. This is a forum that will be edited once the 7.2.x version goes into RC/stable!!

My personal intention for 7.2 is to speed up the internals as optimal a possible for all IDE's. Hope you can help?! Have fun with testing 7.2
Post Reply
Passeti
Fresh Boarder
Fresh Boarder
Posts: 4
Joined: 04.02.2025, 12:11

Catastrophic Failure

Post by Passeti »

Hi
I'm having a problem with memory allocation, where catastrophic failure ends up happening, I couldn't find a pattern for what happened, but there comes a certain time when the component ends up not being able to correctly calculate the size of the field and passes an absurd value, as shown in the print below:
https://prnt.sc/2MxdYF8eJzSl

The value that is passed:
https://prnt.sc/MFpqN2qRRNDG

For the time being, we treat it that way (workaround):
https://prnt.sc/786jsUVLDI-C

print of error:
https://prnt.sc/lnTPlwOpdqIv

if anyone can help me, I appreciate it, we have several customers with this problem! :D
Passeti
Fresh Boarder
Fresh Boarder
Posts: 4
Joined: 04.02.2025, 12:11

Re: Catastrophic Failure

Post by Passeti »

Correct field size photo:
https://prnt.sc/M3UlL96VU3iK
marsupilami
Platinum Boarder
Platinum Boarder
Posts: 2008
Joined: 17.01.2011, 14:17

Re: Catastrophic Failure

Post by marsupilami »

Hello,

could you please check if the problem still exists with Zeos 8? If possible, please test the latest 8.0-patches branch from Subversion or Github.

Can you try to create a sample application that generates the problem, so it is more easy to debug?

Best regards,

Jan
Passeti
Fresh Boarder
Fresh Boarder
Posts: 4
Joined: 04.02.2025, 12:11

Re: Catastrophic Failure

Post by Passeti »

Hello marsupilami,

The error does not occur consistently, and we have been unable to identify a specific pattern that triggers it every time in the project. However, in some cases involving very heavy queries, the error happens repeatedly. After implementing the treatment I mentioned earlier, the issue no longer occurs. For testing purposes, I updated to version 8.0 and am currently attempting to simulate the problem to identify a pattern or reproduce the error.

Another detail is that the same command that is sent in the query is executed without errors in the database, bringing the data without problem.

I am using Delphi 10.3 and Firebird 3.0. The issue was initially found in Zeos version 7.2.6, and it persists in version 7.2.14
Passeti
Fresh Boarder
Fresh Boarder
Posts: 4
Joined: 04.02.2025, 12:11

Re: Catastrophic Failure

Post by Passeti »

Hello, regarding the previously reported problem, our development team found a possible cause of the catastrophic failure problem, being the “ControlsPageCode = cGET_ACP” and the “AutoEncodeStrings = True”, now that we are in version 7.2.14, it is forcing us to use the “CodePage = cCP_UTF16” and as seen in the character set guidelines that you recommended, we disabled the “AutoEncodeStrings” option.
About 3 years ago we migrated to delphi 10.3 and did not convert the database to UTF8, so recently the connection configuration may have been the possible cause of the above problem, we are validating if this already solves the problem of storage in memory, we consulted the coders at the link below:

https://sourceforge.net/p/zeoslib/wiki/ ... er%20sets/
marsupilami
Platinum Boarder
Platinum Boarder
Posts: 2008
Joined: 17.01.2011, 14:17

Re: Catastrophic Failure

Post by marsupilami »

Passeti wrote: 11.02.2025, 15:42 Hello, regarding the previously reported problem, our development team found a possible cause of the catastrophic failure problem, being the “ControlsPageCode = cGET_ACP” and the “AutoEncodeStrings = True”, now that we are in version 7.2.14, it is forcing us to use the “CodePage = cCP_UTF16” and as seen in the character set guidelines that you recommended, we disabled the “AutoEncodeStrings” option.
About 3 years ago we migrated to delphi 10.3 and did not convert the database to UTF8, so recently the connection configuration may have been the possible cause of the above problem, we are validating if this already solves the problem of storage in memory, we consulted the coders at the link below:

https://sourceforge.net/p/zeoslib/wiki/ ... er%20sets/
Wow - I didn't remember writing that... Anyway - for your use case the Suggestion is to use UTF8 as the connection character set, set AutoEncodeStrins to false and use cCP_UTF16 as the ControlsPageCode - which probably is forced by Zeos now.

A note about talking UTF8 with the database: Your database doesn't need to be converted to UTF8 (or UTF16) to use this. But using UTF8 when talking to the database means that Zeos will not do Character set translations. Your database usually is much better with these things...
Post Reply