"Load More Stack Frames" is incorrectly displayed after debug adapter has sent the full stack

Type: <b>Bug</b> Sometimes when landing on a breakpoint, VS Code displays the thread's call stack followed by "Load More Stack Frames" even though the debug adapter has sent all of the stack frames. A simple repro that is working fairly reliably for me is to put two breakpoints in a function a few levels deep. In my case my debug adapter reports a stack with 4 entries. 1. Start debugging 2. Hit the first breakpoint (everything is correct) 3. Wait 2 or 3 seconds (not sure it matters how long but I figured I should wait until all communication with the debug adapter is complete) 4. Press F5 5. Hit the second breakpoint Upon hitting the second breakpoint, the thread list (which was reported in an identical manner from the debug adapter) is incorrectly followed by "Load More Stack Frames". Here is the full dump of all of the json sent between VS Code and my debug adapter when following the above steps: (Note: all stack frame IDs after the first are just `1` because they don't actually represent anything meaningful in my case. I usually send them with "presentationHint":"label", but I removed that while simplifying my code for this test case.) ``` To debugger (t 372): { // Hit first breakpoint "body":{ "allThreadsStopped":true, "reason":"breakpoint", "threadId":1 }, "event":"stopped", "seq":13, "type":"event" } From debugger (t 388): { // One stack frame requested "arguments":{ "levels":1, "startFrame":0, "threadId":1 }, "command":"stackTrace", "seq":12, "type":"request" } To debugger (t 389): { // One returned, totalFrames 4 "body":{ "stackFrames":[ { "id":268435456, "name":"A" } ], "totalFrames":4 }, "command":"stackTrace", "request_seq":12, "seq":14, "success":true, "type":"response" } From debugger (t 390): { "comm…