mirror of
https://github.com/juce-framework/JUCE.git
synced 2026-01-10 23:44:24 +00:00
Prior to this commit it was possible for the WebBrowserComponent implementation on Windows to end up in an infinite loop if multiple WebBrowserComponent objects were being created at the same time. When an instance was already being created, the createWebView() call for the second would place it in a queue and return without initiating its creation. When the first WebView finishes creation, it calls the handleAsyncUpdate() function of the second. However handleAsyncUdpate() would see that the webViewBeingCreated helper variable was already true and not call createWebView(), hence the second WebView would never be created. If, in the meantime, the scriptsWaitingForExecution variable wasn't empty, handleAsyncUpdate() would endlessly call triggerAsyncUpdate(). |
||
|---|---|---|
| .. | ||
| java/app/com/rmsl/juce | ||
| javaopt/app/com/rmsl/juce | ||
| javascript | ||
| juce_ActiveXComponent_windows.cpp | ||
| juce_AndroidViewComponent.cpp | ||
| juce_AppleRemote_mac.mm | ||
| juce_HWNDComponent_windows.cpp | ||
| juce_NSViewComponent_mac.mm | ||
| juce_NSViewFrameWatcher_mac.h | ||
| juce_PushNotifications_android.cpp | ||
| juce_PushNotifications_ios.cpp | ||
| juce_PushNotifications_mac.cpp | ||
| juce_SystemTrayIcon_linux.cpp | ||
| juce_SystemTrayIcon_mac.cpp | ||
| juce_SystemTrayIcon_windows.cpp | ||
| juce_UIViewComponent_ios.mm | ||
| juce_WebBrowserComponent_android.cpp | ||
| juce_WebBrowserComponent_linux.cpp | ||
| juce_WebBrowserComponent_mac.mm | ||
| juce_WebBrowserComponent_windows.cpp | ||
| juce_XEmbedComponent_linux.cpp | ||