That is the problem. I free once but sometimes the regex is runned twice.
Thanks for a lot!
At 2012-03-07 02:46:21,Nicola Fontana n...@entidi.it wrote:
Il giorno Fri, 2 Mar 2012 11:00:46 +0800 (CST)
Xi Yang jianding...@163.com ha scritto:
Hi, everyone!
I use Glib's regular expression
Il giorno Fri, 2 Mar 2012 11:00:46 +0800 (CST)
Xi Yang jianding...@163.com ha scritto:
Hi, everyone!
I use Glib's regular expression in a cycle, and find a rapid memory
consumption increase. Did I forget to release anything?
Thanks a lot!
A working example would be better. Anyway,
On 03/02/2012 04:00 AM, Xi Yang wrote:
Hi, everyone!
I use Glib's regular expression in a cycle, and find a rapid memory consumption
increase. Did I forget to release anything?
since nobody replied I'll give it a shot (without any C++ knowledge):
does seq.header.c_str() return a newly
No it does, not I already cross-read it and it looks fine, did you
give it a shot with valgrind?
Regards
Bernhard Schuster
Am 5. März 2012 15:43 schrieb Olivier Sessink oliviersess...@gmail.com:
On 03/02/2012 04:00 AM, Xi Yang wrote:
Hi, everyone!
I use Glib's regular expression in a
On 03/05/2012 04:56 PM, Bernhard Schuster wrote:
No it does, not I already cross-read it and it looks fine, did you
give it a shot with valgrind?
no I did not, the comment was based just on your code. What does
valgrind report on your code?
Olivier
Regards
Bernhard Schuster
Am 5. März
Hi, everyone!
I use Glib's regular expression in a cycle, and find a rapid memory consumption
increase. Did I forget to release anything?
Thanks a lot!
= code below ==
GRegex* regex_illumina = g_regex_new(
