[Deluge] #3317: dictionary changed size during iteration

5 views
Skip to first unread message

Deluge

unread,
Nov 2, 2019, 11:08:36 AM11/2/19
to delug...@googlegroups.com
#3317: dictionary changed size during iteration
----------------------------+-------------------
Reporter: JohnDoee | Type: bug
Status: new | Priority: minor
Milestone: needs verified | Component: Core
Version: 2.0.0 | Keywords:
----------------------------+-------------------
In my own plugin I create a server using reactor.listenTCP and in the
disable function, I run "stopListening" to clean up.

When the plugin is loaded and I shut down Deluge, I get the "dictionary
changed size during iteration" exception. The problem stems from this
line: https://github.com/deluge-
torrent/deluge/blob/develop/deluge/component.py#L451

If I change self.components.values() to list(self.components.values()) it
all goes away.

--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3317>
Deluge <https://deluge-torrent.org/>
Deluge Project

Deluge

unread,
Nov 12, 2019, 10:41:19 AM11/12/19
to delug...@googlegroups.com
#3317: dictionary changed size during iteration
-----------------------+-------------------
Reporter: JohnDoee | Owner:
Type: bug | Status: new
Priority: minor | Milestone: 2.0.4
Component: Core | Version: 2.0.0
Resolution: | Keywords:
-----------------------+-------------------
Changes (by Cas):

* milestone: needs verified => 2.0.4


--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3317#comment:1>

Deluge

unread,
Nov 12, 2019, 2:43:24 PM11/12/19
to delug...@googlegroups.com
#3317: dictionary changed size during iteration
-----------------------+--------------------
Reporter: JohnDoee | Owner:
Type: bug | Status: closed

Priority: minor | Milestone: 2.0.4
Component: Core | Version: 2.0.0
Resolution: Fixed | Keywords:
-----------------------+--------------------
Changes (by Cas):

* status: new => closed
* resolution: => Fixed


Comment:

Fixed in [ed4bc5fa17ec5]

--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3317#comment:2>

Reply all
Reply to author
Forward
0 new messages