Bugzilla – Bug 1223985
zypper-changelog-plugin exhausts all memory
Last modified: 2024-06-04 04:14:57 UTC
Even with only one available update pending, the changelog plugin uses all available memory and is then killed by the kernel: ----------------------------------------------- $ zypper list-updates v | Update repository | ansible | 2.9.27-bp155.2.16 | 2.9.27-150000.1.17.2 | noarch $ /usr/bin/time -v zypper changelog --update '/usr/bin/zypper-changelog' was killed by signal 9 (Killed) Command exited with non-zero status 137 Command being timed: "zypper changelog --update" User time (seconds): 13.42 System time (seconds): 1.82 Percent of CPU this job got: 96% Elapsed (wall clock) time (h:mm:ss or m:ss): 0:15.84 Average shared text size (kbytes): 0 Average unshared data size (kbytes): 0 Average stack size (kbytes): 0 Average total size (kbytes): 0 Maximum resident set size (kbytes): 3516412 Average resident set size (kbytes): 0 Major (requiring I/O) page faults: 583 Minor (reclaiming a frame) page faults: 643267 Voluntary context switches: 19144 Involuntary context switches: 2383 Swaps: 0 File system inputs: 508840 File system outputs: 256 Socket messages sent: 0 Socket messages received: 0 Signals delivered: 0 Page size (bytes): 4096 Exit status: 137 ----------------------------------------------- That's 3.3 GB of memory here, a bit too much :) $ rpm -q zypper-changelog-plugin zypper zypper-changelog-plugin-0.3-150500.1.1.noarch zypper-1.14.71-150400.3.45.2.x86_64
Forwarding the bug to the changelog plugin maintainer
I have an improved version of the tool under testing. It would be helpful to test in different environments with different update state.
The 0.4-1.1 version is released in Factory/openSUSE Tumblweed.