✅ Download x64dbg 1.0.1837 (commit 203a6a2b29 by @foralost)

Hm, I think it would be better to select based on the “closest” address since most likely the number of rows updates in an application with high memory pressure… I’ll take a look when I’m back home!

Hm, Im thinking about some delta like oldAdresses - currAddress, but im wondering what if there are multiple entries which are 'equally' distant?

... or maybe something more sophisticated

How about storing the currently-selected base+size and selecting the region that overlaps (or is just before) the previous range?

How about storing the currently-selected base+size and selecting the region that overlaps (or is just before) the previous range?

Ok, soooooo we would be interested in selecting only the region based on selected address?
Like:
User clicks address -> We find the base address & size -> We store them -> We select the whole region (base address + sections and stuff)

*** the memory updates ***
aaand tbh what now?

We look at the old base address -> We fetch its new base address & size -> We find the intersection (common range/addresses) -> We select now the intersected range?

It could be something like this:

void updateMemoryMap():
  oldStart = getCellUserdata(firstSelectedRow, ColAddress)
  oldEnd = getCellUserdata(lastSelectedRow, ColAddress) + getCellUserdata(lastSelectedRow, ColSize)

  firstSelectedRow = 0, lastSelectedRow = 0
  for(const region : memoryMap)
    if region.base < oldStart:
      firstSelectedRow++
    if region.base < oldEnd:
      lastSelectedRow++

    setCellContent(...)

  setSelection(firstSelectedRow, lastSelectedRow)

Since regions (lines) in the memory map never overlap each other there will be a few possibilities:

• We just find a region where region.base == oldStart
• The region was split, we will select the first region that overlaps with the old selection
• The region was freed, we will select the first region before the oldselection

The problem starts when multiple regions are selected, the algorithm for selecting the first region will work fine in this case but the part with lastSelectedRow is just made up and need experimentation...

Another issue will be with the sorting, in that case there isn't much we can do except find the first selected region and then just expanding the selection down with the same amount as initially.

Ok, will try to work on it this weekend ;)