[ISSUE] xbps-remove memory leak

[ISSUE] xbps-remove memory leak

[xeroxslayer]

[-- Attachment #1: Type: text/plain, Size: 2621 bytes --]

New issue by xeroxslayer on void-packages repository

https://github.com/void-linux/void-packages/issues/54157

Description:
### Is this a new report?

Yes

### System Info

Void 6.12.11_1 x86_64 GenuineIntel uptodate rrrmFFFFFFFF

### Package(s) Affected

xbps-0.59.2_3

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

Not have a memory leak.

### Actual behaviour

It has a memory leak if certain conditions are met (eats up CPU and mem). I believe a certain package update triggers the issue... or it may be just random, I don't know to be honest. It also seems to be triggered right after an update/restart, but I'm not certain about this either. It has happened on a number occasions now to just dismiss it as a random bit flip or something similar. And it has been happening for about a year now.

To be honest, I wouldn't have noticed it if I didn't ran old hardware on spinning drives with a little RAM (4GB to 8GB), but since I do, the memory leak became fairly evident. CPU goes to 100% on all cores and mem usage just keeps rising very fast (all memory is eaten up in a matter of 10, 20 seconds maybe). Of course, the system is unresponsive then. This might not be the case if you're running Void on an SSD and newer hardware, since it'll throw mem in swap fairly fast, so the system most probably will be responsive, just a bit sluggish.

I suspect a kernel update might be the event that triggers this behavior, but as I said, I'm not certain, I'll have to investigate further.

Also, if you stop the process (Ctrl + C) and run the command again, this doesn't happen. Basically, what I am certain of is that this happens only the first run of `xbps-remove` after an update.

The hardware setups I've noticed this mem leak was these 2.

CPU: Intel Core i7 930
MB: Intel DX58SO
RAM: 6GB (Tripple channel, 3 x 2GB DDR3 DIMMs)
HDD: 500GB (Spinning drive)

CPU: Intel Core2 Quad Q9550
MB: JW Technology JW-IG41M-HD
RAM: 4GB (Dual channel, 2 x 2GB DDR2 DIMMs)
HDD: 250GB (Spinning drive)

### Steps to reproduce

1. Update (`xbps-install -Suv`). It's also preferable that the update also updates the kernel (see above for reason).
2. Reboot.
3. Trigger cleanup (`xbps-remove -ROov`).

CPU should hit the roof for about a second or so, and then drop and HDD/SSD usage should go up after that (doing the actual cleanup). That's the normal behavior. When the memory leak happens, the CPU usage never drops and mem usage just keeps rising till the system becomes unresponsive... and then you just have to restart the rig manually.

Re: xbps-remove memory leak

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 194 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/54157#issuecomment-2626983123

Comment:
xbps issues should be filed on the xbps repo 

Re: [ISSUE] [CLOSED] xbps-remove memory leak

[xeroxslayer]

[-- Attachment #1: Type: text/plain, Size: 2522 bytes --]

Closed issue by xeroxslayer on void-packages repository

https://github.com/void-linux/void-packages/issues/54157

Description:
### Is this a new report?

Yes

### System Info

Void 6.12.11_1 x86_64 GenuineIntel uptodate rrrmFFFFFFFF

### Package(s) Affected

xbps-0.59.2_3

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

Not have a memory leak.

### Actual behaviour

It has a memory leak if certain conditions are met (eats up CPU and mem). I think a certain package update triggers the issue... or it may be just random, I don't know to be honest. It has happened on a number occasions now to just dismiss it as a random bit flip or something similar. And it has been happening for about a year now.

To be honest, I wouldn't have noticed it if I didn't ran old hardware on spinning drives with a little RAM (4GB to 8GB), but since I do, the memory leak became fairly evident. CPU goes to 100% on all cores and mem usage just keeps rising very fast (all memory is eaten up in a matter of 10, 20 seconds maybe). Of course, the system is unresponsive then. This might not be the case if you're running Void on an SSD and newer hardware, since it'll throw mem in swap fairly fast, so the system most probably will be responsive, just a bit sluggish.

I suspect a kernel update might be the event that triggers this behavior, but as I said, I'm not certain, I'll have to investigate further.

Also, if you stop the process (Ctrl + C) and run the command again, this doesn't happen. Basically, what I am certain of is that this happens only the first run of `xbps-remove` after an update.

The hardware setups I've noticed this mem leak was these 2.

CPU: Intel Core i7 930
MB: Intel DX58SO
RAM: 6GB (Tripple channel, 3 x 2GB DDR3 DIMMs)
HDD: 500GB (Spinning drive)

CPU: Intel Core2 Quad Q9550
MB: JW Technology JW-IG41M-HD
RAM: 4GB (Dual channel, 2 x 2GB DDR2 DIMMs)
HDD: 250GB (Spinning drive)

### Steps to reproduce

1. Update (`xbps-install -Suv`). It's also preferable that the update also updates the kernel (see above for reason).
2. Reboot.
3. Trigger cleanup (`xbps-remove -ROov`).

CPU should hit the roof for about a second or so, and then drop and HDD/SSD usage should go up after that (doing the actual cleanup). That's the normal behavior. When the memory leak happens, the CPU usage never drops and mem usage just keeps rising till the system becomes unresponsive... and then you just have to restart the rig manually.

Re: xbps-remove memory leak

[xeroxslayer]

[-- Attachment #1: Type: text/plain, Size: 179 bytes --]

New comment by xeroxslayer on void-packages repository

https://github.com/void-linux/void-packages/issues/54157#issuecomment-2627320930

Comment:
Oh, sorry, I'll close this one.