Closed GoogleCodeExporter closed 9 years ago
Based on the context, I think it's pretty clear that this is a once-off
initialisation that makes an allocation that sticks around for the lifetime of
the process.
Original comment by fullung@gmail.com
on 29 Jul 2013 at 12:26
Thanks for the report. But as mentioned on an earlier comment, this is an
intentional one-time-initialization "leak". We intentionally do not attempt to
clean it up on process exit (think of environments where other threads are
running and potentially using the global object).
Original comment by san...@google.com
on 29 Jul 2013 at 3:33
Original issue reported on code.google.com by
Pavel.Pimenov@gmail.com
on 26 Jul 2013 at 10:37