[tahoe-dev] memory leakage

[Iantcho Vassilev]

Thanks Zooko,

Unfortunately there is no incidents files in that period of time. there are
2 for some time in october...
Now as the client is restarte would that be helpfull to push  "Report a
bug"?
Also i gues have to do it on the machine that happened but is there a CLI
command for that, otherwise i will do port forwarding to get to the WUI.


Iantcho

On Wed, Nov 14, 2012 at 1:24 AM, Zooko Wilcox-O'Hearn <zooko at zooko.com>wrote:

> Thank you for the bug report!
>
> This sounds like a relatively bad bug. We try not to tolerate memory
> over-usage bugs. I've marked #1824 as Priority: Critical.
>
>
> On Mon, Nov 12, 2012 at 6:09 AM, Iantcho Vassilev <ianchov at gmail.com>
> wrote:
> >
> > There is nothing interesting in twistd.log..
> > Should i send incidents dir.. to investigate.?
>
> Yes, please!
>
> https://tahoe-lafs.org/trac/tahoe-lafs/wiki/HowToReportABug
>
> I just added the following useful information to that wiki page:
>
> It is also helpful if you go to the "Welcome Page" of your Tahoe-LAFS
> WUI and scroll to the bottom, where there is a button, labelled
> "Report an Incident". If you push that button, the gateway will write
> out a new incident report file into the "logs/incidents" directory.
>
> Regards,
>
> Zooko
>
> https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1824# Tahoe process gone
> wild
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20121114/cfa1f66c/attachment.html>