Opened 4 years ago

Closed 3 years ago

#1535 closed defect (no response)

Unusual memory usage pattern

Reported by: xmz Owned by:
Priority: minor Milestone: undecided
Component: router/general Version: 0.9.19
Keywords: memory, graph, heap Cc:
Parent Tickets:



On a router with the following details I am seeing a memory usage pattern that looks to be out of the ordinary to me:

I2P version: 0.9.19-0
Java version: Oracle Corporation 1.7.0_76 (OpenJDK Runtime Environment 1.7.0_76-b13)
Wrapper version: 3.5.20
Server version: 8.1.16.v20140903
Servlet version: Jasper JSP 2.1 Engine
Platform: FreeBSD amd64 10.1-RELEASE-p6
Processor: Sandy Bridge H/M (corei)
Jbigi: Locally optimized native BigInteger library loaded from file
Encoding: UTF-8
Charset: UTF-8

I have attached two graphs plotting average memory used, one for a short time interval and the other for a longer time interval.

Please take a look.



Attachments (3)

i2p-15_apr_2015.png (16.5 KB) - added by xmz 4 years ago.
averagememory usage over 4 days
i2p-15_apr_2015.2.png (16.5 KB) - added by xmz 4 years ago.
average memory usage over 4 days
i2p-2-15_apr_2015.png (19.7 KB) - added by xmz 4 years ago.
average memory used over 91 days

Download all attachments as: .zip

Change History (6)

Changed 4 years ago by xmz

averagememory usage over 4 days

Changed 4 years ago by xmz

average memory usage over 4 days

Changed 4 years ago by xmz

average memory used over 91 days

comment:1 Changed 4 years ago by xmz

  • Keywords heap added
  • Type changed from task to defect

So ordinary to me, is stable memory usage. Out of the ordinary are the spikes which nearly use up all available memory.

This may help track down the cause of this memory usage pattern:

4/14/15 12:59:54 AM CRIT [mer tS9o 1/4] net.i2p.util.SimpleTimer2 : Streaming Timer tS9o: Timed task net.i2p.client.streaming.impl.Connection$ResendPacketEvent@74e2238a exited unexpectedly, please report
     java.lang.OutOfMemoryError: Java heap space

comment:2 Changed 4 years ago by zzz

  • Status changed from new to infoneeded_new

Patterns like that are generally caused by client activity, e.g. running some i2psnark torrents for a while, then turning them off (or having them complete). Going floodfill and then non-floodfill is also a possibility.

If the memory usage kept going up, we'd call it a memory leak somewhere, but if not, it looks normal to me.

In any case, there's not enough information here to be able to investigate. If you have any other info, please provide it.

comment:3 Changed 3 years ago by xmz

  • Resolution set to no response
  • Status changed from infoneeded_new to closed

Closing. Nothing unusual.

Note: See TracTickets for help on using tickets.