The longer I run REDasm on my Windows 10 machine the less responsive the application becomes. Granted, I'm on a low-end laptop but the application slows progressively the longer I have it running; causing frequent restarts to get it back to a responsive state. I'm processing a 2 megabyte XBE file, if that matters.
Below is a screenshot of my Task Manager after running REDasm for 2 hours. I usually restart after 10 minutes, but this shows how heavy the CPU usage becomes. At that point the UI only responded to one mouseover-preview of a subroutine and was frozen after that. Pressing the X-exit button responded after 5-10 seconds of waiting.
The longer I run REDasm on my Windows 10 machine the less responsive the application becomes. Granted, I'm on a low-end laptop but the application slows progressively the longer I have it running; causing frequent restarts to get it back to a responsive state. I'm processing a 2 megabyte XBE file, if that matters.
Below is a screenshot of my Task Manager after running REDasm for 2 hours. I usually restart after 10 minutes, but this shows how heavy the CPU usage becomes. At that point the UI only responded to one mouseover-preview of a subroutine and was frozen after that. Pressing the X-exit button responded after 5-10 seconds of waiting.