RAM usage is extreme during configuration processes and being not released

[djborsi]

Until till now I used the v1.2.22 release, all was fine.
Few days ago I switched to 1.3.0.

My setup runs on the Synology DS220+.
OS: DSM 7.2.1-69057 Update 4
I use Container Manager (see screenshot for detailed version).

Instantly after starting setting the new release from zero I noticed that the webpage "http://watermeter:3000/configure.php.", after pushing "preview" button, loads very slow, like never before.
This brought me to check the RAM consumption.
So each time I push the preview button the RAM usage grows extremely.
What is also weird to me, the usage does not get released, it stays continuously on the high level.
I must stop and start again the watermeter container to get the RAM released.

I am not very aware about such topics, so maybe this is a normal behaviour?

Here screenshots:

After restarting the watermeter container:

[nohn]

Cannot reproduce on my machine with my settings.

• Do you remember which version you were running before?
• Can you please provide your config and a corresponding source image?

[djborsi]

Until the update I used v1.2.22.

I just executed the update in the Container Manager direct.
Then I had to adapt the configuration (I did it manually, field after field), because it was reseted after the update.

The source image etc. everything remained the same.

Configuration page as pdf print:
Watermeter - Configure.pdf

Image on which job is done:

[djborsi]

I just noticed that the same situation happens when I call the debug side.
When you refresh it few times, then the ram usage shown in dsm is also growing and growing.

[djborsi]

I am considering a downgrade to the previous version (v1.2.22.), which was not causing this issue to me.
Can you explain if there are big differences between v1.2.22. and 1.3.0 ?
Are the differences relevant for stability, or for effectiveness of OCR?

[nohn]

Feel free. It's a minor PHP upgrade: v1.2.22...v1.3.0