Open bagipro opened 2 years ago
@bagipro Last time (in #1000) cause was memory usage bar, so try to disable it. Also, I can suggest updating java to the latest version (17).
@skylot Yeah, I actually completely forgot about this report :) I tried to look on jadx-gui. But some reason when I open some tabs, a new server socket thread is launched:
"RMI TCP Accept-0" #57 daemon prio=9 os_prio=31 cpu=2.93ms elapsed=482.32s tid=0x00007fcba0b53800 nid=0x18b3b runnable [0x000070001c9b7000]
java.lang.Thread.State: RUNNABLE
at sun.nio.ch.Net.accept(java.base@14.0.2/Native Method)
at sun.nio.ch.NioSocketImpl.accept(java.base@14.0.2/NioSocketImpl.java:755)
at java.net.ServerSocket.implAccept(java.base@14.0.2/ServerSocket.java:684)
at java.net.ServerSocket.platformImplAccept(java.base@14.0.2/ServerSocket.java:650)
at java.net.ServerSocket.implAccept(java.base@14.0.2/ServerSocket.java:626)
at java.net.ServerSocket.implAccept(java.base@14.0.2/ServerSocket.java:583)
at java.net.ServerSocket.accept(java.base@14.0.2/ServerSocket.java:540)
at sun.management.jmxremote.LocalRMIServerSocketFactory$1.accept(jdk.management.agent@14.0.2/LocalRMIServerSocketFactory.java:52)
at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(java.rmi@14.0.2/TCPTransport.java:413)
at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(java.rmi@14.0.2/TCPTransport.java:377)
at java.lang.Thread.run(java.base@14.0.2/Thread.java:832)
Locked ownable synchronizers:
- <0x00000001c2a38130> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)
Could I be an issue? And do you know what is that thread?
sun.management.jmxremote.LocalRMIServerSocketFactory$1.accept(jdk.management.agent
@bagipro this might be a profiler connection or other monitoring tools you are using
Did disabling memory usage bar help this time?
@skylot Oh, looks like it was enabled. Let me try using jadx-gui for a few days and I will close the issue.
Thanks!
Yeah, it solves the problem (again). Sorry!
I will keep this issue open because I want to run some checks:
Hey!
When I have jadx-gui that finished decompilation and hangs in background, it consumes A LOT of CPU resources. When I run
jstack
, I get the following output:However, I cannot see anything in the output that could lead to such behavior. Do I need to run any other tests to detect the problem?