Usually such a behavior indicates that Java is running out of RAM. Which means the total amount of RAM in your system is too low or the project to be decompiled is too large, or both. How much RAM do you have and what OS and java version do you use?
By default Java reserves up to 70% of your total RAM for Jadx. This can be changed by using a different command-line. See our wiki for details: https://github.com/skylot/jadx/wiki/Troubleshooting-Q&A#out-of-memory-problems

The high CPU usage is caused by the Java garbage collector which tries to squeeze out the last bytes of heap memory and for doing so it reorganizes the whole heap (full garbage cycle). This requires moving next to every object in memory around and as Jadx uses a high number of small objects all CPU cores can get pretty busy for a while.

@srzavin can you share an apk (or app name or a link to apk) which causing halts? This might help to debug this issue.
Also, it is not clear, do you use jadx-cli or jadx-gui? And if it is a jadx-gui what cache mode is set in Preferences->Cache ?

P.S. next time, please don't open both discussion and issue with same question 🥲