Java Crashing w/ latest NoScript

[modeler]

Two of us users, one on Mac OS X 10.4.11 and Firefox, and the other on 10.5.6 and Firefox, have encountered this message:

BetterPrivacy: Error in auto-deletion function: [Exception... "Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsILocalFile.path]" nsresult: "0xc1f30001 (NS_ERROR_NOT_INITIALIZED)" location: "JS frame :: chrome://bp/content/bp.js :: anonymous :: line 1050" data: no]

after updating NoScript to the latest dot-point release today.

Symptoms are that Firefox must be force-quit, and appears not to work reliably.

We will appreciate any suggestions...

[Modeler]

Update:

Deleted both NoScript and BetterPrivacy, re-installed NoScript, and things are working OK again on both machines. Clearly there is a conflict between the current NoScript and BetterPrivacy. We are not trying to 2nd guess which one is at fault, if either.

[Tom T.]

I have both NS and BetterPrivacy, although on Windows, and have never noticed a conflict. Does this occur only on certain sites, or on all that use Flash cookies?
Can you point us to a site so we can try to reproduce the issue? (hopefully someone with access to Mac, which I don't have)

btw, this looks like a JavaScript error rather than a Java error.

[GµårÐïåñ]

Although I know alot of people who use BetterPrivacy in conjunction with other addons without a problem, I personally find it ineffective and more problematic than the purpose it intends to serve and many do report large amounts of conflicts and issues with it. I always tell people, beware of the complications, like taking multiple meds, you need to know who is doing what and how it compounds and what interactions can occur. I can only be sure of one thing, NoScript is written to the most current and advanced compliance standards while I cannot speak for BetterPrivacy, so if I was ever in doubt, I would usually suspect the other addons first. When in rare cases the problem has been NS, Giorgio has been good to immediately correct the problem, but I can hardly remember the last issue like that. Just my two cents.

[Modeler]

I have both NS and BetterPrivacy, although on Windows, and have never noticed a conflict. Does this occur only on certain sites, or on all that use Flash cookies?
Can you point us to a site so we can try to reproduce the issue? (hopefully someone with access to Mac, which I don't have)

btw, this looks like a JavaScript error rather than a Java error.

You're right Tom, it is a JavaScript issue -- I misspoke. Note please that there was no conflict observed prior to updating NoScript to the most recent dot-point release. Cannot point to a site; the error message and subsequent problems with Firefox occur very soon after Firefox is launched, prior to connecting to a site.

We have not re-installed BetterPrivacy, have had no more problems.

[Tom T.]

Before I discovered the add-ons, I used to delete Flash cookies manually. So if you still would like to protect your privacy in this way, that's an option. I created a shortcut on my desktop to the Flash folder, and after leaving a site that used Flash, would double-click the shortcut and empty the folder. Note there are two options: if you wish to delete only the LSO (Local Shared Objects, a/k/a Flash cookies, a/k/a PIE (Permanently Identifiable Elements, their pun on "cookie"), the folder to delete is #SharedObjects. If you also wish to delete the "Settings" storage in the neighboring folder Macromedia.com, then you might as well go back up two levels and delete the entire folder Macromedia. It will be re-created as needed on your next visit to a Flash site.

As mentioned, I don't know the path in Mac. But I'll give it in Windows, if that helps -- or just do a search for "Macromedia" or "#SharedObjects".
c\:documents and settings\USERNAME\application data(hidden by default)\macromedia

Or for a quickie (in Windows),
Start > Run > %appdata% (enter) and the Macromedia folder should be right there.

Better Privacy also deletes DOM storage, but that's configurable in Fx. Go to about:config and in the Filter bar, type dom.stor -- which will be enough to bring up dom.storage.enabled. If "true", double-click to toggle to "false".

The only other service that Better Privacy provides of which I'm aware is the blocking of ping tracking, which NoScript does: NS > Options > Advanced > Untrusted > check "forbid <a ping...>, then click the Trusted tab and if "Allow <a ping...> is checked, uncheck it.

You might like to let the BetterPrivacy developer know of your issue, since NS has been eliminated as a cause, so he can address the issue for others.

Hope this helps.