Parser 2 in Ubiquity 0.5 makes it slow and not functioning!

I'm running on windows XP SP3 and I'm using firefox 3.5.
Add-ons that I am using are cooliris, fire.fm, personas, read it later, twitterfox, and adblock plus. I haven't done a fresh install of Ubiquity 0.5 rather I have updated it from 0.1.9
I will try disabling my all of my add-ons to see if it's the problem.
I will post later with my findings.

Exactly the same problem here, and disabling Parser 2 also made Ubiquity behave as before the upgrade.

Running: Ubiq 0.5, Firefox 3.0.11 (Ubuntu 9.04's current version), Ubuntu Jaunty UNR on a Asus Eee 901

OK. I have disabled all of my add-ons and switch on the parser 2 setting.
Ubiquity is faster then before when the add-ons where enabled. BUT it is slower then when the parser 2 is off.
Now what I have to do is to enable the add-ons one at a time to see which add-on makes Ubiquity 0.5 (parser 2) extra slow.

Here are my findings: adblock plus and twitterfox makes Ubiquity 0.5 parser 2 slightly slow, my other add-ons have no effect on ubiquity. I think that it is the cumulative effect of all the add-ons which makes Ubiquity 0.5 really slow when parser 2 is switched on.
One more annoying think with parser 2 is that it makes the translation command useless. As it cannot auto-detect the language that I have highlighted and I have specify the language not to mention the slow speed. I don't have this problem when parser 2 if off and in the older version of Ubiquity.

I also have this problem. I specially notice that when writing long argument texts, say, to the tweet command.

I have this issue both on FF 3.5 and latest nightly (each day since Ubiquity 05 came out) on Mac OSX 10.5.7.

If you have this problem then please press on "I have this problem" button on the top of the page so that the problem get more noticed and therefore the issue is fixed quicker.

I also have this issue, even with things as simple as googling. In particular, while ubiquity 0.5 rapidly pulls up "google" in response to "go", it remains unusable for a second or so.

I'm using FF3.0.11 on Mac OSX 10.5.7

Thanks, heather! After ray bango's tweet I tested it, and it worked somehow feasibly. But it is still slower than the Parser 1, which boiled things down to one question - why do I need parser 2 for?

cons
- it breaks some old commands that weren't updated
- it is still a bit slower than parser 1, specially when starting to type on the ubiquity cmd line

pros
- ? (i have really no idea, since everything seems to work as it should with parser 1, so unless it is for i18n reasons - which are great, but i won't be using in the near future on my machine -, i don't see any positive change).

But yes, i can consider the initial thread issue as solved, now. Thanks, all!

Thank you very much Heather. The parser 2 in the beta version of Ubiquity is certainly faster then the 0.5.0 version. It does not freeze and can perform some of the basic functions like translation.
HOWEVER, It is still about three to two times than parser 1, which I think is a big issue which needs to be addressed.
Also, one more annoying think is that in parser 2 I have to specify where I live every time I want to check the weather. So I have to type in "weather near London", rather than "we" when parser 1 is on, parser 1 seems to auto-detect where I live which is a good feature that should be activated in parser 2.

Hopefully, In the future updates this issue will be solved completely. As I think that the issue is partly solved for now. Thanks everyone for your support and for taking part in this thread.