Open grisharav opened 5 years ago
@grisharav how can I reproduce it?
Unfortunately I can't share the full recording due to IP protection issues. It happened when I tried to view the flamegraph of .net virtual alloc stacks. Here's a screenshot of the data, not sure it will help:
It doesn't happen for all recordings.
My guess is that it's a matter of some numeric calculation inaccuracies and the size turned out negative in
drawingContext.DrawRectangle( brush, null, // no Pen is crucial for performance new Rect(box.X, box.Y, box.Width, box.Height));
Adam will need a repro to make progress on the bug (or you could debug it). Note that it is likely that if you do a File -> Save it will save the view as an *.PerfView.XML.ZIP file. You can then unzip the file, and then edit it to rename anything that you view as IP to something else (although in most cases peoplemethod names interesting IP). Then open that modified PerfView.XML with PerfVIew and see that it repros. Then you can post that (now free of IP).
Note that if you do Right Click -> Drill Into after selecting a cell that represents only some of the samples you can create a new window with that subset to make the repro smaller (and thus the PerfView.XML file . Thus you may wish to do that first
I have created a full memory dump file using procdump on this exception. It should provide you with all the info needed. PerfView.exe_181220_212613.dmp.zip
Seems I got it today. What I did:
After I got the exception I have saved the perf view file using save as. And finally I put ut on my google drive and here is the link: https://drive.google.com/open?id=1kTCuVyHW33c87ynC1S71nzt7bi6B2Nk-