I sometimes get messages like "[11-18 16:20:00] Torbutton NOTE: NO ORIGIN! Blockng request for: [scrubbed]" in the Firefox error console when I try to reload or navigate through tab history, though navigating through the use of links still works. Also, other extensions are unable to reload tabs. This bug appears to be linked to specific tabs, and persists through (but isn't caused by) a TorButton toggle.
Trac: Username: katmagic
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related.
Learn more.
Please use about:config to set extensions.torbutton.loglevel to 3. This (or any other value less than 4) will turn off safe logging, so that the log message will contain the URL of the request which Torbutton blocked.
I received one of these messages shortly after installing Torbutton 1.3.0-alpha and the other extensions you listed, but it didn't prevent a page from being loaded.
I could not reproduce the ‘NO ORIGIN’ message again, or reproduce this bug, in 30 to 60 minutes of browsing with the above extensions installed in Firefox 3.6.12 on Windows (katmagic was using Fedora 14).
I suspect that this problem is caused by Tab Mix Plus, because that is the only extension (other than Firebug, which I believe is innocent here) in katmagic's list that should manipulate tabs or their properties.
A previous ticket (#1392 (closed)) describes an apparently Linux-specific conflict of Tab Mix Plus (unspecified version) with Torbutton 1.2.5 and other addons, but I have not done enough testing to be certain that this bug is Linux-specific or would not eventually appear on Windows.
This is occurring much more frequently now (with 1.3.1-alpha). It appears that the problem is that ContentPolicy.shouldLoad() (at src/components/cssblocker.js:145 as of g5e74e1d) is getting a null requestOrigin argument. I'm not sure why this would be so; unfortunately, documentation of the matter is rather sparse. It also seems that ContentPolicy.should_load is set when it shouldn't be.
I noticed that this behavior can be triggered if you have turned off referers either through torbutton, through another addon, or directly through firefox. Is this the case for either of you?