Skip to content

chromectrl: a new timer for message loop processing is created for each ChromeWindow instance #129

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
GoogleCodeExporter opened this issue Aug 28, 2015 · 4 comments
Closed

chromectrl: a new timer for message loop processing is created for each ChromeWindow instance #129

GoogleCodeExporter opened this issue Aug 28, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link 

There should be only one global timer running. In the wxpython.py example the 
timer is created and destroyed in wx.App. But in chromectrl it is created for 
each chrome window. Creating multiple timers that call CefMessageLoopWork 
simultaneously might result in performance penalties and an undefined behavior.

Original issue reported on code.google.com by [email protected] on 30 Jul 2014 at 8:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter