Experience with Chrome/Chromium: How stable/reliable is it when used with ferrum_pdf?

[DcsMarionDickten]

I am updating a very old Rails project. In particular, it was necessary that I switch from wicked_pdf+wkhtmltopdf to something else. At first I continued using wicked_pdf since it is very good for producing stand-alone HTML files, and then I fed these to headless Chrome/Chromium directly using the command line.
This experience has been abysmal. First, both Chromium and Chrome produce pages full of errors when starting up, and then they work most of the time. Often they take an unbelievable time to start up and then hang at different places. The last error that gets printed to the stdout usually ends in QUOTA_EXCEEDED or in DEPRECATED_ENDPOINT. And then I need to deal with the zombie process. I have been running both Chrome and Chromium on a rather old Mac (my development machine) and a brand-new Debian Bookworm Docker container and found both Chrome and Chromium to be unreliable on both machines.

Now before I start migrating the project to ferrum_pdf: How reliable is it? I've had a look through the dicussions and have got a mixed impression so far.