Closed GoogleCodeExporter closed 9 years ago
For what it's worth, I'm not aware of any leaks in the standard (non-Windows)
version of RE2. We run with lots of leak checking at Google.
Without more information about the purported leak, there's not much I can do.
Original comment by rsc@golang.org
on 21 Jun 2013 at 4:32
I have no access to a good memory leak tracking tool at the moment so I can't
give more information right now. The next 4 weeks I will be busy but after that
I will try to find a good tool and give more info
Original comment by kukid...@gmx.at
on 21 Jun 2013 at 6:03
Hi,
Most likely this is related to static variables used by the lib. E.g. check out re2.c
GLOBAL_MUTEX(empty_mutex);
static const string *empty_string;
static const map<string, int> *empty_named_groups;
static const map<int, string> *empty_group_names;
So these guys will try to get some memory from the heap and delete after a
return from main.
Most likely you are used some sort of default CRT heap checker. Maybe you could
play with flags: _CrtSetDbgFlag ( _CRTDBG_ALLOC_MEM_DF | _CRTDBG_LEAK_CHECK_DF
) in the first place and also check the addresses that "leaked".
Original comment by DenisKra...@gmail.com
on 2 Jul 2013 at 2:24
Original comment by rsc@golang.org
on 10 Jan 2014 at 1:32
Original issue reported on code.google.com by
kukid...@gmx.at
on 16 Jun 2013 at 2:32