On 2014-12-15 19:43, Nick Mathewson wrote:
> On Wed, Dec 10, 2014 at 2:31 AM, Roger Dingledine wrote:
>> On Sun, Dec 07, 2014 at 01:43:46PM +0100, Logforme wrote:
>>> To me it looks like an attacker that ramped up over a 6 hour period and
>>> then stopped building new circuits. Since the tor proce
On Wed, Dec 10, 2014 at 2:31 AM, Roger Dingledine wrote:
> On Sun, Dec 07, 2014 at 01:43:46PM +0100, Logforme wrote:
>> To me it looks like an attacker that ramped up over a 6 hour period and
>> then stopped building new circuits. Since the tor process still uses all
>> available memory (more than
https://gitweb.torproject.org/tor.git/commit/?id=17ecd04fde2fd98b0cca3afb251b7173e22d3f42
On 10 December 2014 at 17:57, Logforme wrote:
> On 2014-12-10 08:31, Roger Dingledine wrote:
> > Careful with your conclusion there -- because of memory fragmentation,
> > the process can still hold the mem
On 2014-12-10 08:31, Roger Dingledine wrote:
> Careful with your conclusion there -- because of memory fragmentation,
> the process can still hold the memory even when Tor has freed the memory.
htop currently shows 3622/3858 Mem used and 1545/3136 Swap used. (if I
remember correctly it's usually le
On Sun, Dec 07, 2014 at 01:43:46PM +0100, Logforme wrote:
> To me it looks like an attacker that ramped up over a 6 hour period and
> then stopped building new circuits. Since the tor process still uses all
> available memory (more than 24 hours later) I guess the attacker still
> holds some circui
On 2014-12-07 12:20, Roger Dingledine wrote:
> Has anybody else here seen messages like this?
I looked through the old log files and found the following memory messages:
Dec 06 03:33:06.000 [notice] Removed 334229280 bytes by killing 1
circuits; 16401 circuits remain alive.
Dec 06 05:27:25.000 [no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07.12.2014 12:20, Roger Dingledine wrote:
> Has anybody else here seen messages like this?
Some days ago I had a message like that on my relay JPsi2
(F6EC46933CE8D4FAD5CCDAA8B1C5A377685FC521).
Tor's memory consumption is rather high there lately.
O
On Sun, Dec 07, 2014 at 09:52:47AM +0100, Logforme wrote:
> I run the relay Logforme (855BC2DABE24C861CD887DB9B2E950424B49FC3).
> Yesterday I saw new messages in the log file:
> Dec 06 09:28:13.000 [notice] We're low on memory. Killing circuits with
> over-long queues. (This behavior is controlled
I run the relay Logforme (855BC2DABE24C861CD887DB9B2E950424B49FC3).
Yesterday I saw new messages in the log file:
Dec 06 09:28:13.000 [notice] We're low on memory. Killing circuits with
over-long queues. (This behavior is controlled by MaxMemInQueues.)
Dec 06 09:28:16.000 [notice] Removed 10403880
