Just wanted to try scribus' colour management, decided to upgrade it from 1.5
before and ran into a memory runaway problem (noticed as all them web workers
were being killed)..

It's reproducable on my system by simply starting it without a file. If started
with a file as parameter, it will behave normally (about 70MB memory usage) but
show the same behaviour when invoking the file open dialog. Here's a simple way
to try without risk of causing problems:

systemd-run --user --scope --unit=scribus -p MemoryMax=1G -p MemorySwapMax=0
scribus & watch -d -n 0.2 "systemctl status --user scribus.scope"; systemctl
reset-failed --user scribus.scope

Might be because of my only partly up-to-date unstable install, looking forward
to hear whether anyone else can reproduce.