Felix Palmen

Although it might also be related to me upgrading FreeBSD from 12.1 to 12.2 as well, didn't test on 12.1 again. But as 12.1 will be EOL soon anyways, that probably doesn't matter.

definitely. Whatever caused it, it's not in 3.5 (at least for me).

No. Sorry for not getting anywhere with testing... But the problem vanished with 3.5, it's working perfectly fine on FreeBSD (with loaded radeonkms driver).

As I said, I can do the suggested testing myself :) Could you give me the revision numbers of the 3.3 and the 3.4 release and all revisions in between that could be relevant? I really hope FreeBSD didn't kill a laptop here :o This is really bad luck!

Ok first of all, I can do this testing ... but it might take a while, cause as soon as I can confirm the leakage, I have to reboot the machine for the next test :) But I'd happily try, and if there's something to debug, I might be able to do this as well... On the other hand, it could also be a good idea to first check whether anyone else can reproduce the problem. It might even be the case that newer VICE versions just trigger a bug hidden somewhere else, e.g. in the radeonkms driver I use (I use...

Thanks a lot compyx for actually trying something :) With your hints, I could analyze a bit further. First of all: The only VICE in my ports collection is vice 3.3, which seems to get built from the 3.3 tarball, which is quite a bit different from our current trunk. I installed ports during my FreeBSD install. FreeBSD ports are constantly updated in svn, but for fetching them with portsnap, there are two alternatives -- "current" snapshot or quarterly snapshot -- I guess the latter is the default....

Vice 3.4 on FreeBSD triggers heavy swapping activity