Cookie problem?

[seedling]

Here is a problem I have been unable to find a discussion on. If I clear my cookie from deluge and log into my web ui, everything runs fine. I can add and delete things, the up and down speed refreshes about every second, etc. I have all the basic columns, (name, size, progress, down speed, up speed, eta) displayed. However, if I make any changes by adding columns like seeders, peers, tracker, etc I then can't add/delete anything and everything in the ui freezes. I also lose connection to the webserver in 10 or so seconds. If I refresh the page and log in again, everything is still frozen and it kicks me out. But if I go and delete the cookie from the web ui, I can then log in again and everything works fine but of course only the basic columns are displayed. As long as I don't change anything the web ui works great every time I log in. But as soon as I change anything it freezes up and boots me out and stays that way until I delete the cookie. Any ideas?

Thank you

[Cas]

You have to tell us basic information as to what version of Deluge and what browser and version you are using.

[seedling]

I'm running Deluge 1.3.5 and the cookie problem happens on the latest versions of Firefox and Safari.

[Cas]

I cannot replicate this issue. How many torrents and what OS?

[seedling]

I probably have about 70-80 torrents going and I'm on OSX 10.6.8

However, I had a buddy running windows and chrome replicate the problem on his computer. The interesting thing we found that the freezing happens only after the "tracker" column is added. I can add other columns and there is no freezing. Very odd.

[Cas]

Are you using deluge-web or the webui plugin? Also are there any errors in the logs?

[seedling]

I got a note from someone who went on my server and checked things out. He said

"I found that the version of debian in the repository for debian (the OS)has this bug in it.
we can compile deluge from source, and it will not have this bug"

So I'll see if after a reformat, etc, things are ok

[Cas]

Sorry I don't quite understand, do you have any more details on this, what is the actual bug?