BN terminated by Linux kernel OOM killer when saving .bndb

[rotateLeft]

Version and Platform (required):
5.4.9444-dev (9173e40c)
Commercial
Arch Linux 6.19.11-arch1-1
Ryzen 9800X3D 32GB DDR5

Bug Description:
Saving to .bndb after performing a rebase causes BN to consume all available memory until Linux OOM killer terminates BN process.

Steps To Reproduce:
Load 32-bit ntdll.dll, allow analysis to finish
Rebase to 0x77970000, allow analysis to finish
Ctrl+S, save to .bndb
Progress bar stalls at 11%, all available system memory is consumed.
OOM kills BN after ~5 seconds.

Saving to fresh .bndb or overwrite existing results in same behavior.

Issue appears to be specifically tied to / triggered by performing a rebase before saving - doesn't happen if saving immediately after analysis is finished with no rebase performed beforehand.

Expected Behavior:
Saving DB does not consume all available system memory resulting in OOM reckoning.

Binary:
Legit Windows 10 32-bit ntdll.dll pulled from a standard Win10 VM.
SHA256: baeb10cd5b9a00a47f6fc53cf088f6cf708d18a499fbb66457f8dd82f641b368

[rotateLeft]

Update:

After full system update and fresh reboot with nothing running, memory consumption is ~4GB.

Load ntdll.dll, analysis complete, ~7.7GB.

Rebase, ~12GB.

Save .bndb, memory consumption touches 30GB a few times before save completes w/o issue.

In the initial report provided above, VM + browser + apps were running, consuming 8-9GB of memory.

[plafosse]

Looks like there is some malfored Type object causing infinite recursion in the DataBase serialization code.