[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xmlblaster] thread/mem leak?

To: xmlblaster at server.xmlBlaster.org
Subject: Re: [xmlblaster] thread/mem leak?
From: "Póka Balázs" <p.balazs at gmail.com>
Date: Fri, 4 Aug 2006 02:15:46 +0200
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=PgHmVBQXiLJ8qNyA52PSqP8ZP5qtFZyJjLfzZTZbZXXAjPF5nu2rI63zkLZ4YREaVlb92xgXHbUzzSbrei7hehMSAjU7ZIur0hXCl5MurrXkbzdHYor9twY0nTWPzEi0Go+6i8h2tmx8DCxy06j6b2GLF2EowvHyHeSok23j/fA=
In-reply-to: <44CD9D15.5080702 at marcelruff.info>
References: <d425539c0607301610x58007f93kb40e22394e98b01b at mail.gmail.com> <44CD9D15.5080702 at marcelruff.info>
Reply-to: xmlblaster at server.xmlBlaster.org
Sender: owner-xmlblaster at server.xmlBlaster.org

Hi Marcel,

yes, please take the newest xmlBlaster from svn, this simplifies it for us.
Could you then please start xmlBlaster in a tool like OptimizeIt
and see if/how your use case produces leaks?

All right, it's been running for some time now, no problems... will run it through a mem profiler if it pops up again. Maybe under heavier load, but hopefully not. :)

regards,
Balázs Póka

Follow-Ups:
- Re: [xmlblaster] thread/mem leak?
  - From: Marcel Ruff <mr at marcelruff.info>

References:
- [xmlblaster] thread/mem leak?
  - From: "Póka Balázs" <p.balazs at gmail.com>
- Re: [xmlblaster] thread/mem leak?
  - From: Marcel Ruff <mr at marcelruff.info>

Prev by Date: Re: [xmlblaster] XPath Filtering
Next by Date: Re: [xmlblaster] thread/mem leak?
Previous by thread: Re: [xmlblaster] thread/mem leak?
Next by thread: Re: [xmlblaster] thread/mem leak?
Index(es):
- Date
- Thread