Comment 6 for bug 1918474

One can run just the failing test and recreate the issue:
 $ freecadcmd --console --run-test femtest.app.test_open.TestObjectOpen

Checking consumption with that shows that it quickly goes up (2s interval)
$ pidstat -p $(pgrep freecadcmd) -T ALL -tr 2
Linux 5.10.0-14-generic (h-test) 03/15/21 _s390x_ (4 CPU)

11:47:08 UID TGID TID minflt/s majflt/s VSZ RSS %MEM Command
11:47:10 1000 19709 - 226433.50 0.00 1541952 1406260 17.10 freecadcmd
11:47:10 1000 - 19709 226418.50 0.00 1541952 1406260 17.10 |__freecadcmd

11:47:08 UID TGID TID minflt-nr majflt-nr Command
11:47:10 1000 19709 - 452867 0 freecadcmd
11:47:10 1000 - 19709 452837 0 |__freecadcmd

11:47:10 UID TGID TID minflt/s majflt/s VSZ RSS %MEM Command
11:47:12 1000 19709 - 326168.00 1.00 4949828 3360308 40.87 freecadcmd
11:47:12 1000 - 19709 326187.00 1.00 4949828 3360572 40.88 |__freecadcmd

11:47:10 UID TGID TID minflt-nr majflt-nr Command
11:47:12 1000 19709 - 652336 2 freecadcmd
11:47:12 1000 - 19709 652374 2 |__freecadcmd

11:47:12 UID TGID TID minflt/s majflt/s VSZ RSS %MEM Command
11:47:14 1000 19709 - 181738.00 0.00 4949828 4814156 58.56 freecadcmd
11:47:14 1000 - 19709 181719.00 0.00 4949828 4814156 58.56 |__freecadcmd

11:47:12 UID TGID TID minflt-nr majflt-nr Command
11:47:14 1000 19709 - 363476 0 freecadcmd
11:47:14 1000 - 19709 363438 0 |__freecadcmd

11:47:14 UID TGID TID minflt/s majflt/s VSZ RSS %MEM Command
11:47:16 1000 19709 - 0.00 0.00 4949828 4814156 58.56 freecadcmd
11:47:16 1000 - 19709 0.00 0.00 4949828 4814156 58.56 |__freecadcmd

11:47:14 UID TGID TID minflt-nr majflt-nr Command
11:47:16 1000 19709 - 0 0 freecadcmd
11:47:16 1000 - 19709 0 0 |__freecadcmd

11:47:16 UID TGID TID minflt/s majflt/s VSZ RSS %MEM Command
11:47:18 1000 19709 - 186463.00 0.00 8357704 6306020 76.70 freecadcmd
11:47:18 1000 - 19709 186476.50 0.00 8357704 6306020 76.70 |__freecadcmd