Opened 13 years ago

Last modified 13 years ago

#457 closed defect (Works for me)

Cookies aren't cleared with some option combos

Reported by: mikeperry Owned by: mikeperry
Priority: High Milestone:
Component: Applications/Torbutton Version: 1.1
Severity: Keywords:
Cc: mikeperry Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


I am having another problem in that the
cookies are not cleared when I toggle the torbutton.

It was working fine for a while, but now I login to a site while
torbutton is off, obtain some cookies and toggle the torbutton. The
cookies remain. I tried disabling torbutton, exiting firefox and
reenabling it. It corrected itself, i.e. it was clearing the cookies
when it is toggled, but after a while it stopped clearing the cookies

I am running Firefox on XP Pro with all updates.
The current torbutton settings are:
Everything is ticked under Dynamic content tab
Everything is ticked under History tab
First option is selected under Cache tab
First option is selected under Cookies tab
Clear cookies during any browser shotdown is selected under Shutdown tab
Everything is ticked under Headers tab

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (3)

comment:1 Changed 13 years ago by mikeperry

If anyone runs into this bug please note the last 10 or so messages
present in your "Tools->Error Console" and copy and paste them into
this bug. Unfortunately you have to copy them 1 line at a time :(

If you want to dive deeper, what will catch it for sure is to
install venkman:

If you run that thing with the javascript debugger window open (under
Tools), and tell it to "Trace Exceptions" (under Debug->Throw
Trigger), you can watch for any exceptions that scrolled by while you
tried to change Tor state and cookies failed to be cleared. The
downside is you have to keep that debugger window opened all the time,
you can't open it after the fact unless the issue is of the type where
once it starts happening, it keeps happening on every successive
toggle. At which point you can then fire up the debugger and watch for
exceptions/errors as it happens.

Be forwarned however, that telling venkman to "Stop on Exceptions" is
a really good way to render it somewhat unusable.. It can get
difficult to use, as it itself often causes exceptions to be
generated. (That is the downside of using exceptions for all error
reporting :)

comment:2 Changed 13 years ago by mikeperry

From a log from KT, it looks like torbutton is becoming confused as to if
it is actually enabled or not in some circumstances.. Need to pepper the
state changing logic with logs and see what we can find out.

comment:3 Changed 12 years ago by mikeperry

flyspray2trac: bug closed.
No more data, haven't seen this happen myself.

Note: See TracTickets for help on using tickets.