Research, development and trades concerning the powerful Proxmark3 device.
Remember; sharing is caring. Bring something back to the community.
"Learn the tools of the trade the hard way." +Fravia
You are not logged in.
Time changes and with it the technology
Proxmark3 @ discord
Users of this forum, please be aware that information stored on this site is not private.
Hi iceman,
thanks for your efforts,the RRG/IceMan-20200310 has sovled staticnested bug, the "keys/sec" and remaining time value is proper.
but there's another problem, the CPU usage is too high when I execute proxmark3, it's about 40% and one of the core is 100%, and the system fans always run. My System is Windows10 64bit, intel i5 1.6GHz, 8G RAM.
I think the reason maybe is: the shell command waiting loop needs some sleep, just like sleep(500), ms.
Hope it helpful & Best Regards.
Last edited by foryouever (2020-03-18 16:17:16)
Offline
Do you have the same issue running the client direct (client/proxmark3) ?
or just when you are running the schell script (./pm3) ?
Offline
I mean in the windows "cmd " mode, run "proxmark3 com*", not run script. Even pm3 is idle, not running any command, the CPU usage is high.
Usurally, an interactive program will enter a loop, to waiting for next command line. At the end of the loop, add a sleep statment,may solve the CPU usage problem.
I've solved programming problems like this before,but I don't know if it applies. Reference only^_^
Last edited by foryouever (2020-03-11 16:49:09)
Offline
If you think you have a solution for your problem, Feel free to contribute.
Offline
If you think you have a solution for your problem, Feel free to contribute.
The offical repo works, great!
thanks Iceman, best regards.
Offline