[tahoe-lafs-trac-stream] [tahoe-lafs] #1939: memory leak (during check --repair --add-lease)

[tahoe-lafs]

#1939: memory leak (during check --repair --add-lease)
----------------------------+------------------------
     Reporter:  killyourtv  |      Owner:  davidsarah
         Type:  defect      |     Status:  new
     Priority:  normal      |  Milestone:  undecided
    Component:  unknown     |    Version:  1.9.2
   Resolution:              |   Keywords:
Launchpad Bug:              |
----------------------------+------------------------

Comment (by zooko):

 Hey kytv! Good to hear from you again. By the way, have you seen the
 renewed interest in merging #68? Check it out. Lebek is away, so maybe you
 should take it over yourself.

 Anyway, about this bug report: thank you for the bug report! Are you using
 exactly Tahoe-LAFS v1.9.2 as generated from our sources, e.g. https
 ://tahoe-lafs.org/source/tahoe-lafs/releases/allmydata-
 tahoe-1.9.2.tar.bz2, or are you using your branch with the #68 patch, as
 described on [wiki:OSPackages#FoolscapTahoe-
 LAFSpatchedforuseonI2Pwithsupportformultipleintroducers]?

 I have a request: change the {{{APPNAME}}} on line 42 of
 [source:git/setup.py?annotate=blame&rev=ae754e9b15253ea863ced38ebf8cd39ed36fddb4#L42
 setup.py] from {{{allmydata-tahoe}}} to something else like maybe
 {{{tahoe-lafs-i2p}}}. That way I'll never have to wonder again if someone
 else's "1.10.0" is the same as my "1.10.0" when someone reports a bug.

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