https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #131 from Matthew Woehlke ---
> Virtual memory is not a relevant measure of anything useful.
That is neither necessarily true, nor necessarily untrue. While I have seen
instances of processes having huge VIRT that didn't correspond to real
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #130 from David Edmundson ---
Virtual memory is not a relevant measure of anything useful. Only Res + Shared
matter.
If you do think you have an issue with memory and confirm you have
https://codereview.qt-project.org/#/c/224684/ applied pl
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #129 from Matthew Woehlke ---
What's the story with this? Because it is apparently still happening with
qt5-5.11.1-9.fc29.x86_64... (I just killed a plasma that had ballooned to
almost 27G VIRT.)
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=368838
alexander changed:
What|Removed |Added
CC||rot...@gmx.de
--- Comment #128 from alexander ---
https://bugs.kde.org/show_bug.cgi?id=368838
Kelvie Wong changed:
What|Removed |Added
CC||kel...@ieee.org
--
You are receiving this mail b
https://bugs.kde.org/show_bug.cgi?id=368838
Lissanro Rahyen changed:
What|Removed |Added
CC||ma...@science.su
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=368838
cdobr...@gmail.com changed:
What|Removed |Added
CC||cdobr...@gmail.com
--- Comment #127 from cd
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #126 from David Edmundson ---
*** Bug 392505 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #125 from Nate Graham ---
Thanks Rik. I'd love to know what you hear. It would be nice to finally get
this fixed in Kubuntu once and for all.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368838
Darin Miller changed:
What|Removed |Added
CC||darinsmil...@gmail.com
--- Comment #124 from Dar
https://bugs.kde.org/show_bug.cgi?id=368838
Rik Mills changed:
What|Removed |Added
CC||rikmi...@kubuntu.org
--- Comment #123 from Rik Mill
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #122 from Antonio Orefice ---
So, i open another one, it is simpler.
Could you guys please test? It is a plasma js script that will use all of my
memory just re-aligning folderview icons over and over
Here:
https://bugs.kde.org/show_bug.cgi?
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #121 from David Edmundson ---
@Nate
I can't see https://codereview.qt-project.org/#/c/224684/ in the debian
packaging tarball. It's in the debian packaging git repo though.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #120 from Matt Whitlock ---
(In reply to Ovidiu Chi from comment #117)
> > I am running a slideshow of 2560x1600 images every 2 seconds with
> > QSG_RENDER_LOOP=basic
>
> @Matt, You'd have to start the slideshow then, after a little while(
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #119 from Nate Graham ---
Which fix is it lacking, David?
https://codereview.qt-project.org/#/c/224684/
or
https://codereview.qt-project.org/#/c/202781/?
Or both? :/
Either way, I'll go get this fixed...
--
You are receiving this mail b
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #118 from David Edmundson ---
>. I entered `QSG_INFO=1 plasmashell` in the terminal to find out the value,
>but nothing is displayed.
You need to quit the old plasmashell beforehand.
>So it seems Kubuntu 18.04 is set to `basic` by default
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #117 from Ovidiu Chi ---
> I am running a slideshow of 2560x1600 images every 2 seconds with
> QSG_RENDER_LOOP=basic
@Matt, You'd have to start the slideshow then, after a little while(a few
seconds), change the duration (e.g. from 3s to 2
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #116 from Matt Whitlock ---
(In reply to Ovidiu Chi from comment #114)
> Matt, I'm not knowledgeable enough to say which memory leak this is, or the
> precise nature of it, but scrolling the list of widgets doesn't do much for
> my system as
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #115 from Ovidiu Chi ---
(In reply to David Edmundson from comment #112)
> @Ovidiu, A packager stating something doesn't necessarily mean much. Can you
> point me to the packaging code. Also do you have
> https://codereview.qt-project.org/#/
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #114 from Ovidiu Chi ---
(In reply to Matt Whitlock from comment #113)
Matt, I'm not knowledgeable enough to say which memory leak this is, or the
precise nature of it, but scrolling the list of widgets doesn't do much for my
system as you
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #113 from Matt Whitlock ---
(In reply to David Edmundson from comment #112)
> @Matt
> How can you tell what is leaking from looking at comment #0?
There have been at least two distinct memory leaks discussed in this thread.
The original rep
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #112 from David Edmundson ---
@Ovidiu, A packager stating something doesn't necessarily mean much. Can you
point me to the packaging code. Also do you have
https://codereview.qt-project.org/#/c/202781/ which is for a different leak.
@Matt
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #111 from Matt Whitlock ---
(In reply to Ovidiu Chi from comment #110)
Plasmashell *does* still have a memory leak, but it's not the one from this
bug. Actually, it *is* the one from the original report in Comment #0, but this
thread morphe
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #110 from Ovidiu Chi ---
(In reply to Nate Graham from comment #109)
I hate to be the "bad news" guy, but this looks exactly like what you describe
- an ever growing, never-releasing memory problem.
Here is a slideshow video: https://vimeo.
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #109 from Nate Graham ---
The bug was not that plasmashell uses memory, but rather that the usage grew
infinitely and the memory was never released. In Kubuntu 18.04, I'm happily
using a slideshow wallpaper and yes, while plasmashell consume
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #108 from Ovidiu Chi ---
(In reply to David Edmundson from comment #107)
> As for your video, Qt 5.11 isn't out yet, are you sure Kubuntu has it?
Kubuntu has Qt 5.9.5, with a backport of your fix as stated here:
https://bugs.launchpad.net/
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #107 from David Edmundson ---
>Nate, David, will the fix be backported to KDE Neon?
I don't deal with any downstreams. You'll have to ask them.
As for your video, Qt 5.11 isn't out yet, are you sure Kubuntu has it?
--
You are receiving t
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #106 from Ovidiu Chi ---
Thought to give an update.
I'm using Kubuntu 18.04.
The original issue reported here by Antonio seems fixed. Video here:
https://vimeo.com/270079798
The memory leak due to wallpaper changes isn't. Video here:
https:/
https://bugs.kde.org/show_bug.cgi?id=368838
rplanchu...@gmail.com changed:
What|Removed |Added
CC||rplanchu...@gmail.com
--
You are recei
https://bugs.kde.org/show_bug.cgi?id=368838
David Edmundson changed:
What|Removed |Added
CC||kn...@ifi.uio.no
--- Comment #105 from David
https://bugs.kde.org/show_bug.cgi?id=368838
Ovidiu Chi changed:
What|Removed |Added
CC||metalkt...@gmail.com
--- Comment #104 from Ovidiu
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #103 from Nate Graham ---
See my previous comment: this has been fixed in *Qt 5.11*. Ask your distros to
backport the patch to their Qt 5.9.x and 5.10.x packages.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #102 from DeMus ---
KDE 5.12.4, Frameworks 5.45.0, Qt 5.10.1.
When using the slide-show memory is filling up pretty fast.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #101 from Nate Graham ---
Qt 5.10 is closed now, so it will be in Qt 5.11. Ask your distros to backport
it (as Kubuntu already has into the Qt 5.9.5 they'll ship with Kubuntu 18.04:
https://bugs.launchpad.net/ubuntu-rtm/+source/qtdeclarative
https://bugs.kde.org/show_bug.cgi?id=368838
Zakhar changed:
What|Removed |Added
CC|zakhar.nasi...@gmail.com|
--
You are receiving this mail because:
You are watc
https://bugs.kde.org/show_bug.cgi?id=368838
Erick Osorio changed:
What|Removed |Added
CC||evgom@gmail.com
--- Comment #100 from Erick
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #99 from Jason ---
how do I go about changing "QSG_RENDER_LOOP" to threaded? FYI, when I run from
a terminal "QSG_INFO=1 plasmashell" I get nothing back.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368838
David Edmundson changed:
What|Removed |Added
CC||colliso...@osu.edu
--- Comment #98 from David
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #97 from Zakhar ---
(In reply to Jesse from comment #95)
> I tried the patch but the memory leak bug reported in #392568, which was
> marked as a duplicated of this one, still persists for me. So either I'm
> missing something or that bug is
https://bugs.kde.org/show_bug.cgi?id=368838
David Edmundson changed:
What|Removed |Added
CC||zakhar.nasi...@gmail.com
--- Comment #96 from
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #95 from Jesse ---
I tried the patch but the memory leak bug reported in #392568, which was marked
as a duplicated of this one, still persists for me. So either I'm missing
something or that bug is not really a duplicated.
--
You are recei
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #94 from David Edmundson ---
FYI. Merged now into Qt 5.11.0. Due to be released in a few months
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368838
David Edmundson changed:
What|Removed |Added
CC||alex.miha...@gmail.com
--- Comment #93 from D
https://bugs.kde.org/show_bug.cgi?id=368838
Nate Graham changed:
What|Removed |Added
URL||https://codereview.qt-proje
|
https://bugs.kde.org/show_bug.cgi?id=368838
David Edmundson changed:
What|Removed |Added
CC||jesse...@gmail.com
--- Comment #92 from David
https://bugs.kde.org/show_bug.cgi?id=368838
Dr. Chapatin changed:
What|Removed |Added
CC||jan.muss...@gmail.com
--- Comment #91 from Dr. C
https://bugs.kde.org/show_bug.cgi?id=368838
Hannes Schweizer changed:
What|Removed |Added
CC|nilat...@gmx.net|
--
You are receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=368838
Hannes Schweizer changed:
What|Removed |Added
CC||nilat...@gmx.net
--- Comment #90 from Hannes
https://bugs.kde.org/show_bug.cgi?id=368838
David Edmundson changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #88 from Nate Graham ---
(In reply to Gauthier from comment #87)
> Hi,
>
> I have memory leak that occurs without having the slide-show
> So I feel this is a different issue to the one reported here
Please don't report unrelated issues in
https://bugs.kde.org/show_bug.cgi?id=368838
Gauthier changed:
What|Removed |Added
CC||achat1...@free.fr
--- Comment #87 from Gauthier ---
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #86 from David Edmundson ---
Steps to reproduce:
- set to QSG_RENDER_LOOP=basic
- create a slideshow
- open a taskmanager tooltip
- then we leak
Tooltip is not rendered because it's not visible.
But it's re-used so still exists.
QSGGui
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #85 from David Edmundson ---
Lucky timing, just gave up and hit submit.
Had
diff --git a/src/quick/scenegraph/qsgrenderloop.cpp
b/src/quick/scenegraph/qsgrenderloop.cpp
index ca1fb9ba5..a8beac369 100644
--- a/src/quick/scenegraph/qsgrender
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #84 from David Edmundson ---
Now managed to reproduce locally...but not even slightly consistently.
Can someone who has it reliably check if reverting
eeb320bbd8763f3e72f79369cc3908e999a0da3c in QtDeclarative fixes it.
My theory from some
https://bugs.kde.org/show_bug.cgi?id=368838
David Edmundson changed:
What|Removed |Added
Summary|plasmashell memory leak |plasmashell memory leak
|wh
https://bugs.kde.org/show_bug.cgi?id=368838
David Edmundson changed:
What|Removed |Added
CC||kde_bug_rep...@yahoo.com
--- Comment #83 from
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #82 from Anders Lund ---
fredag den 23. marts 2018 14.38.09 CEST skrev du:
> https://bugs.kde.org/show_bug.cgi?id=368838
>
> --- Comment #81 from Alexander Schlarb ---
>
> @Nate Graham:
> > I'm also wondering if there's any disadvantage t
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #81 from Alexander Schlarb ---
@Nate Graham:
> I'm also wondering if there's any disadvantage to always using the threaded
> render loop. Alexander, would you be able to run with it for a while and
> report any regressions, if any?
I've be
https://bugs.kde.org/show_bug.cgi?id=368838
lucazade changed:
What|Removed |Added
CC|luca.for...@gmail.com |
--
You are receiving this mail because:
You are wa
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #80 from Nate Graham ---
Basically, we need to find a path forward here. This bug is getting pretty long
and squirrelly, especialyl considering that it's not our fault. Do we need a
few more Qt bugs, David?
--
You are receiving this mail b
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #79 from David Edmundson ---
> So should Qt use the threaded render loop by default, then? Or should we? Or
> something else?
Is decided by Qt based on your graphic card/drivers.
Maybe that selection code in Qt can be tweaked, but we most
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #78 from Nate Graham ---
We're all aware of the issue's implications, and are trying to fix it.
I'm also wondering if there's any disadvantage to always using the threaded
render loop. Alexander, would you be able to run with it for a while
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #77 from Alexander Schlarb ---
Please just keep in mind that the current first-use experience is absolutely
abysimal for everybody using the described configuration: You log into an
up-to-date system with plasmashell and everything will appe
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #76 from Matt Whitlock ---
(In reply to Nate Graham from comment #74)
> So should Qt use the threaded render loop by default, then? Or
> should we? Or something else?
Presumably the VRAM memory leak in the basic render loop should be found
https://bugs.kde.org/show_bug.cgi?id=368838
David Edmundson changed:
What|Removed |Added
CC||grouchomarx...@gmail.com
--- Comment #75 from
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #74 from Nate Graham ---
(In reply to Matt Whitlock from comment #73)
> There are two issues. QSG_RENDER_LOOP=threaded *does* avoid the VRAM memory
> leak
Thanks Matt. So should Qt use the threaded render loop by default, then? Or
should we
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #73 from Matt Whitlock ---
(In reply to Nate Graham from comment #72)
> So the consensus is that QSG_RENDER_LOOP=threaded doesn't fix the issue?
There are two issues. QSG_RENDER_LOOP=threaded *does* avoid the VRAM memory
leak but *does not*
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #72 from Nate Graham ---
So the consensus is that QSG_RENDER_LOOP=threaded doesn't fix the issue?
It seems like the discussion of this issue should take place in a Qt bug
report, since it's not a KDE issue. https://bugreports.qt.io/browse/Q
https://bugs.kde.org/show_bug.cgi?id=368838
Nate Graham changed:
What|Removed |Added
CC||and...@alweb.dk
--- Comment #71 from Nate Graham
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #70 from David Edmundson ---
Not too surprising. Thanks for reporting back.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #69 from Kishore Gopalakrishnan ---
(In reply to David Edmundson from comment #68)
> There's a branch of plasmashell davidedmundson/wallpaperrewrite
>
> Could someone reliably with this bug build and try it please.
>
> It's not written to
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #68 from David Edmundson ---
There's a branch of plasmashell davidedmundson/wallpaperrewrite
Could someone reliably with this bug build and try it please.
It's not written to specifically fix anything, there is no bug in plasma-side
code,
https://bugs.kde.org/show_bug.cgi?id=368838
kdeb...@levinus.de changed:
What|Removed |Added
CC||kdeb...@levinus.de
--
You are receiving th
https://bugs.kde.org/show_bug.cgi?id=368838
kaito.li...@gmail.com changed:
What|Removed |Added
CC||kaito.li...@gmail.com
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=368838
Rex Dieter changed:
What|Removed |Added
CC||andreyo...@gmail.com
--- Comment #67 from Rex Diet
https://bugs.kde.org/show_bug.cgi?id=368838
Christoph Feck changed:
What|Removed |Added
CC||gle...@gmail.com
--- Comment #66 from Christop
https://bugs.kde.org/show_bug.cgi?id=368838
Christoph Feck changed:
What|Removed |Added
CC||goldma...@gmail.com
--- Comment #65 from Chris
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #64 from Alexander Schlarb ---
I feel like an idiot. I just tried running plasmashell with qt 5.9.4 “again”
and found that it crashes on startup. Looking through my command-history it
seems that all the search paths were slightly wrong *face
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #63 from Matt Whitlock ---
(In reply to Alexander Schlarb from comment #62)
> the RSS memory leak with the nVidia binary
> drivers.
Um, I'm using the open-source AMDGPU driver, and I can easily drive up
plasmashell's VmRss by doing what Ant
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #62 from Alexander Schlarb ---
@Antonio Orefice: Sorry 'bout that. There seemed to be a connection between
these two issues that apparently isn't there.
Since the QSG issue has fixed in Qt 5.9.4 and 5.10.0, I nominate that we close
387341 (
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #61 from Antonio Orefice ---
Exactly.
Exactly what i reported when i opened this bug, see comment #1.
I don't want to be harsh, but this 'bug report' is becoming a mess since it has
been arbitrarily joined/defaced with something unrelated.
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #60 from Matt Whitlock ---
(In reply to Antonio Orefice from comment #59)
> I just made a video showing how plasma can reach about 1GB of ram usage from
> 300MB in a bunch of seconds.
I too can reproduce a rather serious memory leak just by
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #59 from Antonio Orefice ---
I'm glad you guys found a workaround for your particular case.
However, mine (see first post), is still present.
I just made a video showing how plasma can reach about 1GB of ram usage from
300MB in a bunch of se
https://bugs.kde.org/show_bug.cgi?id=368838
boonhead.nl changed:
What|Removed |Added
CC||bugs.kde@boonhead.nl
--- Comment #58 from boo
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #57 from Matt Whitlock ---
(In reply to Marco Martin from comment #50)
> can this be tried again with a more recent Qt? either the latest 5.9 or 5.10
> making sure both of these patches are in:
>
> https://codereview.qt-project.org/#/c/2007
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #56 from Alexander Schlarb ---
That's a typo, the actual command had been issued with `QSG_RENDER_LOOP=basic`.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #55 from Matt Whitlock ---
(In reply to Alexander Schlarb from comment #54)
> `QCG_RENDER_LOOP=basic`.
It's supposed to be QSG_RENDER_LOOP. ("SG" for "scene graph.")
--
You are receiving this mail because:
You are watching all bug changes
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #54 from Alexander Schlarb ---
@Marco Martin: I've tested with the [Qt binary 5.9.4 binary
release](https://download.qt.io/official_releases/qt/5.9/5.9.4/) by setting the
correct `PATH`, `LD_LIBRARY_PATH`, `QML2_IMPORT_PATH` & `QT_PLUGIN_PAT
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #53 from Antonio Orefice ---
QSG_RENDER_LOOP makes no difference to me (i'm not testing media frame widgets
or slideshow wallpaper, see first post).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #52 from gertlink_nos...@gmx.de ---
Plasma 5.12.1
QT 5.10.1
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #51 from gertlink_nos...@gmx.de ---
QSG_RENDER_LOOP=threaded solves the problem here.
Graphics: Card-1: Intel 2nd Generation Core Processor Family Integrated
Graphics Controller
Card-2: NVIDIA GF117M [GeForce 610M/710M/810M/820M
https://bugs.kde.org/show_bug.cgi?id=368838
Marco Martin changed:
What|Removed |Added
CC||notm...@gmail.com
--- Comment #50 from Marco Mar
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #49 from Alexander Schlarb ---
Hmm… At least for me there seems to be a pretty obvious corrolation here:
QSG_RENDER_LOOP=basic→ Memory leak
QSG_RENDER_LOOP=threaded → No issues, no leaking
Can other people confirm this (both wi
https://bugs.kde.org/show_bug.cgi?id=368838
Alexander Schlarb changed:
What|Removed |Added
CC||alexander-...@ninetailed.ni
https://bugs.kde.org/show_bug.cgi?id=368838
Nate Graham changed:
What|Removed |Added
CC||ncogh...@gmail.com
--- Comment #47 from Nate Grah
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #46 from Matthew Woehlke ---
I am also still seeing the issue with Qt 5.9.4, plasma 5.11.5 (full list of my
current packages posted to Bug 388580 so as not to clutter this report).
--
You are receiving this mail because:
You are watching a
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #45 from Antonio Orefice ---
qt5 5.10.0 here.
Memory increases over time as described in the first post, nothing changed.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #44 from gertlink_nos...@gmx.de ---
My current system is QT 5.10.0 and Plasma 5.12.1.
The "memory leak" error is still present, since version QT 5.9.1
If I activate the slideshow in the picture frame applet, I miss about 150 MB of
memory aft
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #43 from Matt Whitlock ---
(In reply to Nate Graham from comment #42)
> Is there anyone using Qt 5.9.2 or beyond who can reproduce this issue?
As I mentioned in comment #36 and comment #38, I am running Qt 5.9.4, and I can
still easily exha
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #42 from Nate Graham ---
That Qt bug was reportedly fixed in 5.9.2. If that's the cause, then anyone
using a later Qt version should be fine.
Is there anyone using Qt 5.9.2 or beyond who can reproduce this issue?
--
You are receiving this
1 - 100 of 130 matches
Mail list logo
