I plan to hit every possible support thread out there. Thanks Stamatgeorge for the other bug report website that I was not aware (I will hit it too, even if it takes a day). My concern is that the AgileBits usegroup moderators seem to have not yet grasped the concept that their extension could be one of, if not THE, culprit for the great Lion Safari memory leak.
Here is my problem: I finally got hooked on Safari many months ago (used to use Firefox) and it has continually improved with each version, but I cannot live without 1Password. So now since updating to Lion, I have to surf on Safari and then switch to Firefox if I need to use 1Password for quick password entry (one of the major reasons for having 1Password to begin with).
I cannot enable the 1Password entension on Safari, or my MBPro becomes unuuseable after a few hours of memory leaks (or I have to restart Safari every few minutes). This is very contra to the Apple mantra of "it just works", which I am a big believer.
Maybe there is more to this, but I am certain 1Password has something to do with it and so far AgileBits does not recognize it (and I have been monitoring their support threads for several weeks now). I appreciate the recommendations for the bug reports, but I would also like to find out if others have duplicate issues so that I know I am not crazy, and mostly so that AgileBits gives this issue its due attention.
Keep in mind that the Safari Web Content structure only came out with Lion, and AgileBits may still be blind to the issues related to the new architecture. As an aside, I also love Zagg products and bought their 1st generation iPad Folio case for my iPad2, the one which would not CLOSE. They shipped me a great replacement, but you have to wonder how that made it out to the public without anyone being sure that it could actually close. I respect Zagg and would buy again, but they missed it big time the first time around. I respect AgileBits as well, but i think they are missing it too with their broken extension.
I normally do not push things in support groups because someone has usually already brought up the issue and someone much smarter than me came up with the answer (or at least the best identified source). But so far after 3-4 weeks, no one seems to be really pointing directly at 1Password as the culprit. Would like to hear some confirmation.