Transmission problem

hello!

Since I updated to Core-Update-Level: 203, the following problems have appeared:

Many services are running, but clamav and transmission use most of the memory, which is not a problem, because there is 32gb of DDR4 memory in the server. When clamav and transmission use about 1gb of memory, they stop and sometimes my whole system crashes. The first picture shows when the machine throws everything away, you can’t log in with ssh or on the web interface. Sometimes I manage to log in on the console, but not always. This is what appears on the monitor at that time. Clamav and transmission were running at that time.

The last time I tried not to start transmission and so I have been error-free for 2 days. However, if I start transmission, transmission crashes after a few hours, in the best case, and in the worst case, my whole system.

All-day log from 2026.09.04.

I’ve now turned transmission back on. If it crashes again, I’ll post that log too.

Looking through your provided log clamav is not mentioned at all.

There are entries for transmission. The key one is

15:24:30 kernel: traps: transmission-da[4000] general protection fault ip:7173b6d67a2b sp:7173b6bf5da8 error:0 in libc.so.6[167a2b,7173b6c28000+168000]

This problem has occurred due to some issue between transmission and the glibc library.

Looking in the transmission github issues, the only GPF is

https://github.com/transmission/transmission/issues/5474

which occurred back in 2023 with an old transmission version. The bug was closed without any fix as the original reporter never followed up with any more data.

The current version since CU202 is 4.1.1 and this has been out since April 2026.

There have been no reports in the transmission github issues related to GPF’s except for that one from 2023.

This looks like there might be some issue maybe with a driver that your hardware uses or some other issue that is causing problems for the transmission software as no other transmission users have reported this GPF.

If the problem repeats then I would suggest that you raise an issue on the transmission github site, showing the error message from your log and provide whatever information/data that they require to investigate this. You will need to create a github login account if you don’t already have one.

Hi!

Thanks for the answer!

I had time today and ran memtest. It threw an error in the first seconds… The problem was due to memory voltage. In the motherboard bios it was set to “Auto”, I changed it to 1.25v, memtest ran without errors, no problems since then. Sorry for the mistake. I’ll start with that next time.

Glad you found the cause :+1: