I doubt it, since these users would be running dashd, not dash-qt. dashd powers all high-use environments, including masternodes and mining pools, and they haven't discovered a memory leak in years of use far more intensive that what the reporter of this bug has seen. It is likely some issue...