> On Apr 1, 2015, at 10:30 AM, Brett Harrison <[email protected]> > wrote: > > I am not a Go programmer but I was hoping to gather some data that would be > useful in finding these leaks.
It’s nearly impossible to inspect Go programs using regular tools, because Go doesn’t use the platform’s calling conventions, stack layout, or memory allocator. (It uses its own lightweight threads and a garbage collector.) At a high level you can watch the total memory usage of the Go process, or its CPU usage, but to get any finer grained than that you have to use Go tools. I do know that the SG team have been doing a lot of work tracking down memory issues lately, so you might try building your own SG from the master branch (it’s pretty easy even if you don’t know Go) and seeing if you still see excessive memory use. —Jens -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/2BE54F2D-F8FB-4B4E-B88E-79E498984E29%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
