As for the memory leak, currently I'm unable to locate the problem. I have a lot of other things to do, like my MSc for instance. If anybody wants to be added to credits, have a look at the extension's code and find it

Chrome 3.0.195.1 (current Dev) introduced a breaking change in page actions, I just updated the extension to 0.3.9.3 to reflect those changes.

I'm aware of the new extensions autoupdate feature, but currently I don't have time to play with it (vide paragraph 1). I think I'll wait for the "extensions gallery" which they say is coming.

@TP

The latest Dev update 3.0.196.2 has stopped the Subscribe button in the Omnibox from working ....

It still displays as it should (both types) but no action is performed when you click on it ...

Everything else seems OK (Apart from the memory thing) ...

Are you sure you have TPGoogleReader version 0.3.9.3? Maybe you need to update it (from the link in the first post). For me it works just fine.

Can't you use resource tracking or some of the other develpoping tools to track the problems ?

I put the project on Google Code, for now only Downloads and Issues are active, maybe later the source code will become available too, if I find time for playing with it.

TPGoogleReader project

So please fill the issues there. And if anybody could please collect any unresolved problems from this thread and fill issues for them too

@TP

Absolutely sure, I've had it installed since the day you released it !!

Guess it doesn't matter for the time being as I've gone back to 3.0.195.4 because of other issues with the release ...

Originally Posted by StevePaul

@TP

The latest Dev update 3.0.196.2 has stopped the Subscribe button in the Omnibox from working ....

It still displays as it should (both types) but no action is performed when you click on it ...

Everything else seems OK (Apart from the memory thing) ...

I have this too.

As explained on the project's Wiki page, this is not my fault, but a Chrome bug that they have already identified and will probably correct in the next Dev release, so be sure to check again once it's there.

Of course it might break something else, in which case I'll have to make necessary changes in the plugin and upload another release. Nevertheless, be sure to check this later.

Thanks for your answer. I hope they fix this issue as soon as possible

Release 0.3.9.4. http://code.google.com/p/tpgooglerea...i/ReleasesList works well for Chromium 4.0.202.0 Windows