[tahoe-lafs-trac-stream] [tahoe-lafs] #1824: Tahoe process gone wild

[tahoe-lafs]

#1824: Tahoe process gone wild
--------------------------+--------------------------------
     Reporter:  kpreid    |      Owner:  daira
         Type:  defect    |     Status:  new
     Priority:  critical  |  Milestone:  1.11.0
    Component:  code      |    Version:  1.9.2
   Resolution:            |   Keywords:  hang repair memory
Launchpad Bug:            |
--------------------------+--------------------------------

Comment (by zooko):

 Replying to [comment:19 kpreid]:
 > > kpreid: what version of Tahoe-LAFS generated the output you show here?
 >
 > The traceback contains a mention of "1.9.0.post28". The same string is
 still in my {{{build/lib/allmydata/_version.py}}}, if that's the right
 place to look. I don't know offhand whether I've updated at all since I
 had this error, but if I haven't the git revision is
 [dd2e7a1127353a608dffb8d4b88f9a28f373e2e1/git] plus the patch at https
 ://tahoe-lafs.org/trac/tahoe-lafs/ticket/1628#comment:7 .

 Great! Then I believe this issue to be fixed in 1.9.2, because it is an
 instance of #1636. Daira, what did you mean in comment:5 by "the unhandled
 exception is causing an infinite deferred loop. Let's fix that separately,
 even if we change this particular case to be handled."? Do you think we
 can close this ticket as as dup of #1636 now?

 kpreid: you could try upgrading to 1.9.2 (or the shiny new 1.10 pre-
 release!) and then let us know if this problem or anything like it ever
 recurs. Thanks for the bug report!

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1824#comment:20>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage