View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0006960||Kali Linux||General Bug||public||2020-12-30 18:40||2021-01-11 09:54|
|Summary||0006960: System Run Away while working with GVM 20.8|
System run away while working with GVM 20.8 which consumes all RAM and fills up complete swap space. In this situation complete system is inaccessible.
|Steps To Reproduce|
In my case I have a scan with about 2500 results in a single report.
Bug 0006763 is still there, but with GVM 20 and PostgrSQL 13.
It seems, that old database searches are still running (the page is still loading) and new searches are added to them.
I think we need an additional function which interrupts old, no longer needed searches when the specific user is starting a new search by changing filter directives.
I was able to get a result of top short before the run-away:
%Cpu(s): 0.5 us, 16.5 sy, 0.0 ni, 0.0 id, 82.7 wa, 0.0 hi, 0.3 si, 0.0 st
191972 _gvm 20 0 11.6g 5.2g 1392 S 39.8 33.6 0:31.21 gsad
It's a matter of some seconds. Now we see that gsad is consuming the memory and filling up swap space. Does we have some kind of memory leak?
The result of top of note #0013956 was taken after login to GSA and complete load of default dashboard.
Duplicate of 0006907
|2020-12-30 18:40||Hakan16||New Issue|
|2020-12-30 18:40||Hakan16||Issue generated from: 0006907|
|2020-12-30 18:41||Hakan16||Issue cloned: 0006962|
|2021-01-10 11:16||kali-bugreport||Note Added: 0014086|
|2021-01-11 09:54||daniruiz||Assigned To||=> daniruiz|
|2021-01-11 09:54||daniruiz||Status||new => closed|
|2021-01-11 09:54||daniruiz||Resolution||open => duplicate|
|2021-01-11 09:54||daniruiz||Relationship added||duplicate of 0006907|