The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Count me out. I, as a CPian, have no interest in beating anyone or anything.
BTW, it is Croatia who is winning the cup this time. If England wins the cup and they tell someone/something already predicted it, I visualize Charlie lad as the next client asking when he would become king.
In visual studio 2017 there is a memory profiler.
You can take memory snapshot at interval of your choice while running a debugging session and compare snapshot for the number of object or bytes taken.
Thing is: when you stop debugging because, say, you want to edit a file, it close all the snapshots!
Now, I found a workaround, if you run snapshot comparison (while debugger is running, obviously) the window stay open.
But, wait for it, if your snapshot comparison has been detached (in my case floating on the other screen), when you stop debugging it is closed! Losing all data collected again!
Look like Microsoft doesn't want us accidentally using the information we just collected. This feature should remain a teaser...