Custom Query (1911 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (13 - 15 of 1911)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Ticket Resolution Summary Owner Reporter
#610 fixed Lost bote indentities after update to 0.8.13 HungryHobo gadoon
Description

After updating to 0.8.13 i don't have any i2pbote identity. I just started using bote, but i don't think this is a normal behaviour, right?

#686 fixed "GC loop of death" example with 0.9.1-5 HungryHobo Zlatin Balevsky
Description

"user" on #i2p-dev has been kind enough to forfeit his anonymity and provide us with a heap dump after observing the "GC Loop Of Death". Heap dump for jhat analysis from his router as well as wrapper logs are available here:

http://t5qds7twb7eyyvp2fchhbn74tgdzv774rlru5guit5jkn4a6do7a.b32.i2p/dump/

description of the gc loop of death available here http://pastethis.i2p/show/1587/

a preliminary look at the logs suggests seedless may be to blame, but with OOMs you never know.

#690 fixed Bote and/or seedless creating too many connection objects HungryHobo Zlatin Balevsky
Description

"user" reported a router halt. Lots of stack traces available here:

http://t5qds7twb7eyyvp2fchhbn74tgdzv774rlru5guit5jkn4a6do7a.b32.i2p/again/

Looking at stack_20 for example we see that one of the runner threads is holding the I2PTunnelRunner.slock monitor while waiting for some other operation to finish. A ton of other I2PTunnelRunner threads are blocked waiting to acquire the same monitor.

"I2PTunnelRunner 8198" daemon prio=10 tid=0x00007f59545d5800 nid=0x7011 in Object.wait() [0x00007f593b7f6000]
   java.lang.Thread.State: TIMED_WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        at net.i2p.client.streaming.Connection.packetSendChoke(Connection.java:214)
        - locked <0x00000000f7972570> (a java.util.TreeMap)
        at net.i2p.client.streaming.PacketLocal.waitForAccept(PacketLocal.java:215)
        at net.i2p.client.streaming.MessageOutputStream.flushAvailable(MessageOutputStream.java:490)
        at net.i2p.client.streaming.MessageOutputStream.flush(MessageOutputStream.java:341)
        at net.i2p.client.streaming.MessageOutputStream.flush(MessageOutputStream.java:305)
        at net.i2p.i2ptunnel.I2PTunnelRunner.run(I2PTunnelRunner.java:161)
        - locked <0x00000000e2d6aea0> (a java.lang.Object)

There are some other problems in his report, such as 28468 instances of net.i2p.client.streaming.Connection. It is unclear if they are the cause or the result of the above condition. I'll be updating this post if I gain more insight.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Note: See TracQuery for help on using queries.