If i disable the memory graph, the resource claim growth is immediately
reduced.
The GC i was talking about, are X11 Graphic Contexts.
Gr. Simon
On 9/5/23 23:16, Michael Bien wrote:
hi Simon,
On 04.09.23 11:00, Simon IJskes - QCG wrote:
It does take long before netbeans to rise to the top, and some time
later rendering artifacts start to occur. These are solved (so it
looks) by clicking on the graph forcing GC.
This would indicate that UI resources are freed during object
finalization (or equivalent). This wouldn't be a good strategy since it
correlates two independent resources with each other (although I have
seen this done in past in other projects). Its like only refueling your
car if the water bottle is empty.
I can't reproduce this right now and never saw something like this
happening while using NetBeans, but if this is the case and we can
figure out what it is, we should take a look at it.
The memory graph in the performance toolbar claims a huge amount of
X11 resources.
When looking at xrestop you can see it growing every second.
why do you think that the memory graph is causing this? Maybe I am
missing something but I read the other mails too and don't see the
connection. You can turn it off, see below.
During the search for this behaviour, i also noticed the applet cannot
be removed from the toolbar. Drag operation does not work, which it
does on the other buttons in the performance toolbar.
right click on empty tool bar space -> uncheck "Performance"
The rate of GC increments depends on if the performance toolbar is the
last in the toolbars, when i add a custom toolbar at the end, it is
down to 3 per second. When not about 30+ per second.
How did you measure this? 3 GCs per second in the young generation would
be completely normal, 3 in the old generation would be very suspicious.
Finalization does also only happen in certain GC phases and is
implementation dependent (one reason why its deprecated for removal).
Clicking the memory graph should run it if G1 is used.
I'm starting to think it is a broader problem. Maybe more a LAF thing,
if i 'hide' the window...
NB does far more than just rendering text and buttons. It could scan
your projects for changed files or run other periodic tasks. Those tasks
are usually suspended when you minimize the main window - you might be
measuring something here you don't intend to.
make sure you test with the latest JDK update release to exclude runtime
bugs (maybe its even a X11 bug),
best regards,
michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
--
create firmware without programming https://www.bendyroad.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
