https://bugs.kde.org/show_bug.cgi?id=507217
--- Comment #17 from [email protected] --- (In reply to Aleix Pol from comment #12) > Any of the people who can reproduce the issue, we'd very much appreciate > some testing. > > Alternatively, could you see if the process ends after about 80s of closing > it? My processes all disappear with time, but that amount of time is highly chaotic (out of order from the time the process threads are initialized). The first thread I try to make (aka the first time I try to click the icon to open after closing it), it creates a process that never decays to shutting down. That process is unique in the amount of memory it takes up. It is consistently just over 40MB, while any other Discover process spawned while the first one is sitting there (failing to open anything) only takes up ~32MB. Clearly, duplicate Discover processes are somehow different from that first attempted reopening, regardless that none of them work. I will attach an image to this issue showing the different RAM usage for the duplicates when I open excessive (stuck) instances. Anyway, to repeat, the time it takes for those 32MB excess processes to shut down is highly chaotic, some taking just a dozen seconds and some taking multiple whole minutes. -- You are receiving this mail because: You are watching all bug changes.
