2.46 Cookie Manager Crashes

[Bob Fam1]

I just tried to use the Tools/Cookie Manager in SM 2.46. It opens in a minimized window which cannot be resized and crashes the Manager and SM. I cannot delete a cookie that I wanted removed. The SM 2.40 Cookie Manager worked fine before I updated to 2.46.

Is there a fix?

Bob.

[barbaz]

Works for me. What if you set about:config > suite.manager.dataman.openAsDialog to false ?

[Bob Fam1]

HI. Thanks. That fixed the size of the window but when I try to type in a domain it crashes and crashes SM. Did you actually try typing in a domain name and if so did it show the domain for editing?

I read the 2.46 release notes and it says:

"The option to ask about cookies was removed from the Mozilla backend code. The functionality could not be duplicated in our code and had to be removed."

Does this mean we can no longer manage cookies?

2.46 is buggy. Can we reinstall 2.40?

Bob.

[therube]

The option to ask about cookies was removed from the Mozilla backend code. The functionality could not be duplicated in our code and had to be removed.

That is something different.
This option was removed from FF (& now carried forward into SeaMonkey):

[Bob Fam1]

Hi. Are you saying 2.46 should look like your picture? Mine does not have "Ask for each cookie". When you click on Cookie Manager does yours work and are you able to edit any domain? Mine crashes. If yours does how can I fix mine. I want to delete a cookie like I could do in 2.40.

Thanks, Bob.

[therube]

No, that feature was removed from FF (& now SeaMonkey).

[therube]

> I want to delete a cookie like I could do in 2.40.

Any change if you restart SeaMonkey in http://kb.mozillazine.org/Safe_mode ?
Does Cookie Manager then work?

[barbaz]

when I try to type in a domain it crashes and crashes SM. Did you actually try typing in a domain name and if so did it show the domain for editing?

No, I didn't try that. I open SeaMonkey 2.46, visit a site that sets cookies (e.g. this forum), then go to Tools > Cookie Manager > Manage Stored Cookies.

In the resulting screen, where are you trying to type in a domain?

EDIT
If you're typing it in the "Search Domains" box, that works for me too, so please do follow the troubleshooting suggestions from therube and let us know the results.

[frg]

Its just javascript and shouldn't crash. Do you have a crash id?

[frg]

Try the old cookie viewer:

chrome://communicator/content/permissions/cookieViewer.xul

[TPR75]

I just tried to use the Tools/Cookie Manager in SM 2.46. It opens in a minimized window which cannot be resized and crashes the Manager and SM. I cannot delete a cookie that I wanted removed. The SM 2.40 Cookie Manager worked fine before I updated to 2.46.

Is there a fix?

Since option "ask every time" for cookies was removed I'm using Cookie Monster 1.3.4.8 but it requires conversion and some "tuning":
http://forums.mozillazine.org/viewtopic ... #p14714447
Tuning is for correct view and deleting cookies if required.

If you don't know how to modify it you can download mine XPI:
https://mega.nz/#!g1ITHRqI!UweoY-3R4Ero ... ljV1yA8h7c
(SHA256: d080ff23eb65fdb468d36af69469ad11b666435a02ed14982c90f9718b737630)

In options (within Add-ons Manager) set "Block all cookies" and then enable them when needed for particular sites. In theory you can use SeaMonkey own/internal function (Ctrl + i -> Permissions) but 3rd party cookies can't be managed this way.

IMHO "ask every time" option was better because sometimes CM can't handle sub-domains correct (especially for 3rd party cookies).
E.g. at site trailers.apple.com:
- blocking cookies for "www.apple.com",
- allowing cookies for "trailers.apple.com",
- allowing cookies for "movietrailers.apple.com".

I did above when I had SeaMonkey 2.40 (without Cookie Monster extension). But when I tested it on Adrian's SM 2.46/2.47 with CM 1.3.0.5 (on new profile) then Cookie Monster never showed/detected 3rd party cookies for "movietrailers.apple.com".

When I tested Mega.nz service with Mega own extension then it was not possible (at least for me) to use it together with Cookie Monster because Mega.nz ask for cookies for Mega.co.nz (and makes other stuff like changing https to "something other") and CM can't handle such things.

Some sites with captcha have problem too.

[Bob Fam1]

when I try to type in a domain it crashes and crashes SM. Did you actually try typing in a domain name and if so did it show the domain for editing?

No, I didn't try that. I open SeaMonkey 2.46, visit a site that sets cookies (e.g. this forum), then go to Tools > Cookie Manager > Manage Stored Cookies.

In the resulting screen, where are you trying to type in a domain?

EDIT
If you're typing it in the "Search Domains" box, that works for me too, so please do follow the troubleshooting suggestions from therube and let us know the results.

Thanks. No it does not work in normal or safe mode.Bob.

[Bob Fam1]

I just tried to use the Tools/Cookie Manager in SM 2.46. It opens in a minimized window which cannot be resized and crashes the Manager and SM. I cannot delete a cookie that I wanted removed. The SM 2.40 Cookie Manager worked fine before I updated to 2.46.

Is there a fix?

Since option "ask every time" for cookies was removed I'm using Cookie Monster 1.3.4.8 but it requires conversion and some "tuning":
http://forums.mozillazine.org/viewtopic ... #p14714447
Tuning is for correct view and deleting cookies if required.

If you don't know how to modify it you can download mine XPI:
https://mega.nz/#!g1ITHRqI!UweoY-3R4Ero ... ljV1yA8h7c
(SHA256: d080ff23eb65fdb468d36af69469ad11b666435a02ed14982c90f9718b737630)

In options (within Add-ons Manager) set "Block all cookies" and then enable them when needed for particular sites. In theory you can use SeaMonkey own/internal function (Ctrl + i -> Permissions) but 3rd party cookies can't be managed this way.

IMHO "ask every time" option was better because sometimes CM can't handle sub-domains correct (especially for 3rd party cookies).
E.g. at site trailers.apple.com:
- blocking cookies for "www.apple.com",
- allowing cookies for "trailers.apple.com",
- allowing cookies for "movietrailers.apple.com".

I did above when I had SeaMonkey 2.40 (without Cookie Monster extension). But when I tested it on Adrian's SM 2.46/2.47 with CM 1.3.0.5 (on new profile) then Cookie Monster never showed/detected 3rd party cookies for "movietrailers.apple.com".

When I tested Mega.nz service with Mega own extension then it was not possible (at least for me) to use it together with Cookie Monster because Mega.nz ask for cookies for Mega.co.nz (and makes other stuff like changing https to "something other") and CM can't handle such things.

Some sites with captcha have problem too.

Thanks.
Thanks. No it does not work in normal or safe mode.Bob.

[Bob Fam1]

Its just javascript and shouldn't crash. Do you have a crash id?

Here is waht I get:

Log Name: Application
Source: Application Hang
Date: 12/28/2016 6:56:07 AM
Event ID: 1002
Task Category: (101)
Level: Error
Keywords: Classic
User: N/A
Computer: Bob_Win7PC
Description:
The program seamonkey.exe version 49.0.2.6191 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 33c
Start Time: 01d2611a6f279390
Termination Time: 10
Application Path: C:\Program Files (x86)\SeaMonkey\seamonkey.exe
Report Id: bffea684-cd0d-11e6-9d79-0026833b6566

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Hang" />
<EventID Qualifiers="0">1002</EventID>
<Level>2</Level>
<Task>101</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-12-28T14:56:07.000000000Z" />
<EventRecordID>836063</EventRecordID>
<Channel>Application</Channel>
<Computer>Bob_Win7PC</Computer>
<Security />
</System>
<EventData>
<Data>seamonkey.exe</Data>
<Data>49.0.2.6191</Data>
<Data>33c</Data>
<Data>01d2611a6f279390</Data>
<Data>10</Data>
<Data>C:\Program Files (x86)\SeaMonkey\seamonkey.exe</Data>
<Data>bffea684-cd0d-11e6-9d79-0026833b6566</Data>
<Binary>55006E006B006E006F0077006E0000000000</Binary>
</EventData>
</Event>

Why does it say 49.0.2.6191?
I have Version 2.46.

Thanks, Bob.

[Bob Fam1]

Try the old cookie viewer:

chrome://communicator/content/permissions/cookieViewer.xul

Thanks. How do you use this? Bob.