fix(runtime-core): remove all blocks related to the current instance to avoid memory leaks in ssr

[HcySunYang]

close: #3100

[HcySunYang]

I created a new project based on the project provided by @aprilcai, which provides four heap memory snapshots:

• leak.start.heapsnapshot
• leak.end.heapsnapshot
• healthy.start.heapsnapshot
• healthy.end.heapsnapshot

And, you can directly load these snapshots into chrome and analyze memory leaks, u can also execute the following two commands to generate a snapshot locally:

yarn heapdump-leak
yarn heapdump-healthy

My analysis result is:

[LinusBorg]

@HcySunYang which priority label is this? More of a common situation or an edge case?

[HcySunYang]

I think it's an edge case because it only occurs when rendering errors

[yyx990803]

Actually, since there can never be nested renderComponentRoot calls, we can just always reset blockStack when there's a render error. See da944cb