[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: Bug: main.c:344: connection_stop_writing

To: or-talk@xxxxxxxxxxxxx
Subject: Re: Bug: main.c:344: connection_stop_writing
From: Olaf Selke <olaf.selke@xxxxxxxxxxxx>
Date: Thu, 11 Oct 2007 05:59:20 +0200
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Wed, 10 Oct 2007 23:59:37 -0400
In-reply-to: <20071010194554.GX20802@xxxxxxxxxxxxxx>
References: <470D2AD1.30402@xxxxxxxxxxxx> <20071010194554.GX20802@xxxxxxxxxxxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.13 (Windows/20070809)

Roger Dingledine wrote:
> On Wed, Oct 10, 2007 at 09:41:05PM +0200, Olaf Selke wrote:
>>
>> Is this a known bug?
>>
> Yes, but it isn't fixed:
> http://bugs.noreply.org/flyspray/index.php?do=details&id=451
> 
> If you can help fix it, that would be grand. :)

oooh, better I don't since my coding capabilities are very limited :-) On my wishlist is a
fix for the memory leak which lets the tor process grow to about 2GB workspace after two
weeks and better multiprocessor support.

Olaf

Follow-Ups:
- Re: Bug: main.c:344: connection_stop_writing
  - From: Nick Mathewson

References:
- Bug: main.c:344: connection_stop_writing
  - From: Olaf Selke
- Re: Bug: main.c:344: connection_stop_writing
  - From: Roger Dingledine

Prev by Author: Bug: main.c:344: connection_stop_writing
Next by Author: Re: magic Wednesday
Previous by thread: Re: Bug: main.c:344: connection_stop_writing
Next by thread: Re: Bug: main.c:344: connection_stop_writing
Index(es):
- Author
- Thread