RESOLVED FIXED 73814
[Qt] Remove redundant m_glWidget->makeCurrent() calls in GraphicsContext3DQt.
https://bugs.webkit.org/show_bug.cgi?id=73814
Summary [Qt] Remove redundant m_glWidget->makeCurrent() calls in GraphicsContext3DQt.
Dongseong Hwang
Reported 2011-12-05 03:07:20 PST
GraphicsContext3DQt's all APIs call m_glWidget->makeCurrent(). It causes a performance hit, especially in the page that has multi webgl contexts.
Attachments
patch (43.59 KB, patch)
2011-12-05 03:16 PST, Dongseong Hwang
no flags
Patch (43.76 KB, patch)
2011-12-16 21:41 PST, Dongseong Hwang
noam: review-
webkit.review.bot: commit-queue-
patch (43.72 KB, patch)
2011-12-18 16:04 PST, Dongseong Hwang
no flags
Dongseong Hwang
Comment 1 2011-12-05 03:16:47 PST
Noam Rosenthal
Comment 2 2011-12-05 08:13:12 PST
Comment on attachment 117863 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=117863&action=review Good patch, insufficient ChangeLog. > Source/WebCore/ChangeLog:8 > + Reviewed by NOBODY (OOPS!). Insufficient Changelog. Please describe that you've moved all the calls into makeContextCurrent.
Dongseong Hwang
Comment 3 2011-12-05 15:13:28 PST
That's simple reason. I followed GraphicsContext3DOpenGL.cpp. There are two options. 1. makeContextCurrent(); 2. m_private->makeCurrentIfNeeded(); I chose 1 option. Do you think I should describe above explanation in Changelog?
Dongseong Hwang
Comment 4 2011-12-05 17:35:37 PST
Comment on attachment 117863 [details] patch I want your response again, because there is no special reason.
Noam Rosenthal
Comment 5 2011-12-09 22:14:00 PST
(In reply to comment #3) > That's simple reason. I followed GraphicsContext3DOpenGL.cpp. > > There are two options. > 1. makeContextCurrent(); > 2. m_private->makeCurrentIfNeeded(); > > I chose 1 option. > > Do you think I should describe above explanation in Changelog? Not really, just say something like "moved the redundant function calls to makeContextCurrent()" should be enough.
Dongseong Hwang
Comment 6 2011-12-16 21:41:53 PST
WebKit Review Bot
Comment 7 2011-12-16 22:28:15 PST
Comment on attachment 119714 [details] Patch Attachment 119714 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/10922016 New failing tests: http/tests/inspector/resource-tree/resource-tree-document-url.html
Noam Rosenthal
Comment 8 2011-12-17 08:01:32 PST
Comment on attachment 119714 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=119714&action=review > Source/WebCore/ChangeLog:9 > + Need a short description and bug URL (OOPS!) Remove this line > Source/WebCore/ChangeLog:14 > + No new tests. (OOPS!) > + You say "No new functionality so no new tests"
Dongseong Hwang
Comment 9 2011-12-18 16:04:55 PST
Created attachment 119784 [details] patch I'm sorry for my carelessness.
Noam Rosenthal
Comment 10 2011-12-18 16:18:04 PST
(In reply to comment #9) > Created an attachment (id=119784) [details] > patch > > I'm sorry for my carelessness. It's no problem, we all forget this stuff once in a while :)
WebKit Review Bot
Comment 11 2011-12-18 18:08:04 PST
Comment on attachment 119784 [details] patch Clearing flags on attachment: 119784 Committed r103203: <http://trac.webkit.org/changeset/103203>
WebKit Review Bot
Comment 12 2011-12-18 18:08:10 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.