Louis Ye 叶绿宇
Louis Ye 叶绿宇
I was able to reproduce the memory leak on both GAE standard and locally deployed application. The key to reproduce is to have an active logpoint that is set at...
Further investigation shows that, the "memory leak" is not caused by the code in cloud debugger, but rather it is caused by the fact that the v8 inspector session stored...
Storing each of the breakpoint hit context might be a feature provided by v8 inspector, but as for the usage of cloud debugger, this is not what was needed, because...
A bug on the V8 Engine is opened about the related issue: https://bugs.chromium.org/p/chromium/issues/detail?id=1208482
Hi @kilianc and @rhodgkins, I wasn't able to reproduce the memory leak without setting active breakpoints. The fix (for fixing memory leak when having active breakpoints) was just merged in,...
* Is this separate tool already available today? * Is the scope of this bug limited to using this tool (if available) in pprof?
It is possible that this is coming from two different functions, it is just that we strip the parameters part. Also, `pprof -http=:` doesn't help to reproduce this issue; if...
@mauri870 Can you attach the profile for easier debugging?
https://github.com/google/pprof/pull/798 is addressing this issue.