-
Notifications
You must be signed in to change notification settings - Fork 79
Open
Description
I have implemented logic to trace my program's logic units' interaction using graphviz diagram(it is huge one with dozen MB each), and I found each time I rendered the svg file, my go process memory shoot up significantly and it doesn't come down to expected level after garbage collected. (I have properly called the rendered graph's close and the graphviz instance's close for each call)
From golang's pprof tool, I can see the WASM part is retaining huge amount of memory

I created instance of graphviz in each call and after rendered the svg file, I close both, should I only create one global graphviz instance instead ?
graphviz.New(ctx)
Metadata
Metadata
Assignees
Labels
No labels