50% CPU usage about edit-this-cookie

[fcapano]

From [email protected] on September 07, 2012 10:03:01
Hi, sorry to hear that. Does it happen when you open the popup/options page, or also right after opening chrome browser?

[fcapano]

From [email protected] on September 07, 2012 10:08:29
Can you also tell me which version of Edit This Cookie are you using? There ave been different updates yesterday, so please check that you are using the latest version (1.1.10)

[fcapano]

From [email protected] on September 15, 2012 16:48:52
The issue should be fixed in version 1.1.20. Let me know if you still have problems!

[fcapano]

From [email protected] on September 17, 2012 23:53:40
I am using 1.1.21 and it is consistently taking 28-33% CPU, according to Chrome Task Manager. It only seems to happen after chrome has been open for a while.
Thanks

[fcapano]

From [email protected] on September 18, 2012 09:49:32
Do you have any cookies blocked or protected?
Are you using the option to shorten the cookies' maximum age?
Do you have any extension's page open when the issue appears?

Could you do the following while the extension's cpu usage is high?:

• Go to "chrome://chrome/extensions/"
• Ensure "Developer mode" is enabled
• Go to "Edit This Cookie"
• Click on "_generated_background_page.html"
• Go to console
• Copy and paste here
• Back to the console, Right-click -> Clear console
• Does it stay empty or new messages appear?

Thank you for your time, hopefully this time I'll be able to fix the issue for real

[JonasNo]

This function gets into an infinite loop:
background.js line 60 -> "chrome.cookies.onChanged.addListener( function(changeInfo) {"

changeinfo:
cause: "overwrite"
cookie: Object
removed: true

The function "chrome.cookies.get" at line 84 executes the callback function with currentCookie = null.
That cause an exception in "compareCookies" line 89.
"cookie_helpers.js:99 Cannot read property 'name' of null"

The function "compareCookies" returns false after the exception. Than calls "chrome.cookies.set(newCookie);" at line 92 in background.js

This causes an infinite loop.

"chrome.cookies.set" cause "chrome.cookies.onChanged" to be called and it repeats.

The infinite loop starts somehow when chrome is idle for a period of time.

[fcapano]

I don't think there's been any report regarding this in a long time, I'll close this issue.