Luke Hoersten wrote: > I've stopped using FF 2 completely because its so slow on Linux. I > have the same problems you are describing, Luis, but with all plugins > and FF, not just mozcc. Perhaps this problem is with FF's plugin > interface. >
I doubt it. Even if I weren't predisposed to doubt it, it wouldn't fit with Luis's experience of degraded performance between versions of MozCC: it'd be a consistent (or probably at least linear) degradation regardless of which extensions or versions you had installed. Instead it seems more likely that we've changed something that exercises the browser in a different way. Hrm, that's an idea, actually... most of the changes in this update happened in the RDFa module. You can download a build with RDFa disabled at http://mirrors.creativecommons.org/software/mozcc/download/mozcc-2.3.9.1-nordfa.xpi. I'd be interested in hearing if that fixes the performance problems for anyone experiencing them. Thanks, Nathan > -Luke > > On 1/22/07, Luis Villa <[EMAIL PROTECTED]> wrote: >> On 1/22/07, Nathan R. Yergler <[EMAIL PROTECTED]> wrote: >>> I admittedly didn't do much testing without MozCC installed v. with it >>> installed, but rather between the old and new version. So I'll take a >>> look as well and see if its something I might have missed. >> FWIW, I've been using mozcc religiously (given the conflict, I >> disabled operator, not mozcc ;) so my first comparison was between old >> and new mozcc. >> >> Luis >> >>> Luis Villa wrote: >>>> On 1/22/07, Nathan R. Yergler <[EMAIL PROTECTED]> wrote: >>>>> An updated version of MozCC is now available for testing. Version 2.3.9 >>>>> is a recommended update as it resolves a number of outstanding issues >>>>> including: >>>>> >>>>> * Rewrite of the RDFa extraction engine which no longer pollutes >>>>> Javascript prototypes >>>>> * Performance enhancements when extracting RDFa from documents >>>>> * Interoperability fixes with other extensions >>>> For what it is worth, Nathan, this fixes the interoperability problems >>>> I had with Operator[1] but the new plugin seems to completely degrade >>>> ffox performance on most of the pages I used- took several times >>>> longer to load my blog and mail.google.com. This happens with or >>>> without Operator installed, so it isn't the result of an interaction >>>> with Operator. >>>> >>>> Is anyone else seeing this? I don't have time (class shortly) to >>>> uninstall/disable *all* of my plugins, but I'm guessing if Nathan >>>> didn't see it it must be an interaction with some other plugin, so >>>> I'll have to back everything out later tonight if no one else is >>>> seeing it. >>>> >>>> Luis >>>> >>>> [1] https://addons.mozilla.org/firefox/4106/ >>>> _______________________________________________ >>>> cc-devel mailing list >>>> [email protected] >>>> http://lists.ibiblio.org/mailman/listinfo/cc-devel >>> >>> -- >>> Nathan R. Yergler >>> Senior Software Engineer >>> Creative Commons >>> >>> http://wiki.creativecommons.org/User:NathanYergler >>> >> _______________________________________________ >> cc-devel mailing list >> [email protected] >> http://lists.ibiblio.org/mailman/listinfo/cc-devel >> > > -- Nathan R. Yergler Senior Software Engineer Creative Commons http://wiki.creativecommons.org/User:NathanYergler _______________________________________________ cc-devel mailing list [email protected] http://lists.ibiblio.org/mailman/listinfo/cc-devel
