Memory listing in Developer Console does not sort properly when requested

[EmeraldSlash (Rio)]

Some memory categories won’t display in correct order when the user has requested it (by clicking the “Value MB” column header to toggle the sorting direction). Turning the sorting off and on again does not fix the problem.

It seems to happen in all groups, but it’s particularly annoying with the PlaceScriptMemory group since that’s the stuff I’m trying to sort.

Memory usages outlined in red are out of order:

Expected behavior

Clicking the “Value MB” column header should properly sort all entries by their value in this column. (IMO when in sorted mode the list should update automatically so that entries are always in sorted order, but perhaps that’s more of a feature request than a bug since if we want latest results we should be able to just toggle the sorting off and on.)

[thirdtakeonit]

Thanks for the report! We’ll follow up when we have an update for you.

[MetaVars]

We are looking into this as part of a dev console update.

[Sir_Highness]

I have an unrelated question. Why are scripts being grouped into one memory size value? For example in this screenshot:

[Camstcha]

They’ve stated why on both threads talking about memory view tabs:

@WheretIB

By default, the memory category name is the name of the script. Custom memory category names can be assigned using the debug.setmemorycategory function. Multiple scripts often share the same memory category slot as their number is limited.

Continuing the discussion from Developer Console: Update for Luau Memory Use Tracking:

@WheretIB

To keep the overhead of memory tags extremely low, there are implementation-defined limits for the amount of script and user memory tags. Because of this, you might see a single row sharing more than one script/tag name.

Keep in mind that a Luau thread has an associated memory tag and not the specific script instance. If your script calls a function defined in ModuleScript, allocations made there will be tracked by the calling script thread.

[PotionSeller33]

We’ve rolled out a fix to make the “Value MB” column header actually re-sort the column if you click it while the header is already selected. This will let you “refresh” the sorting by memory size. This won’t continuously re-sort though, so the rows will stay stable until you click the header again.