NTRRemoteDebugger icon indicating copy to clipboard operation
NTRRemoteDebugger copied to clipboard

Slow

Open colt05-usr opened this issue 8 years ago • 7 comments

Hello! When searching memory, this goes slow. Any way to speed it up? Thanks.

colt05-usr avatar Sep 18 '16 12:09 colt05-usr

What are the criteria you're looking for? DataType, Value, Memregion(s), ...

phecdaDia avatar Sep 19 '16 14:09 phecdaDia

All of the Memregions, that's probably why.

colt05-usr avatar Sep 20 '16 23:09 colt05-usr

Also, do I need to click Open again to do the next search?

colt05-usr avatar Sep 21 '16 00:09 colt05-usr

No, you should be able to just change the value you're searching for and refine the results.

phecdaDia avatar Sep 21 '16 00:09 phecdaDia

There's not really a way to speed up memory searches beyond what's already in place, unfortunately. The 3DS's wifi is slow, and we can't ask the 3DS to search for a specific byte set in memory because NTR CFW does not have such a feature. Unfortunately, these features are in the .bin for NTR and not in the actual C++ source, so we can't contribute a feature back to NTR for this either.

valarnin avatar Sep 22 '16 00:09 valarnin

But to make it faster, you can't dump the 1st memory dump, and then search the value directly in the dumped file ? Should be faster.

JustForNothing avatar Nov 20 '16 18:11 JustForNothing

To clarify, the way it works is that there's a threshold where if there are more than 200 results currently found for a search, it will dump the entire memory region selected to search, then compare only the valid addresses from that region. Otherwise, it dumps memory for each address in the results collection and compares them.

We can't keep comparing values from the first memory dump, that wouldn't have any updated values in it.

This parameter should really be moved to the configuration settings GUI, but I won't have time to work on this project in general until the new year unfortunately.

valarnin avatar Nov 23 '16 23:11 valarnin