David Benjamin

Hrm, so it does. Fancy.

Though even if the viewer never times out, we may still need to communicate nested event loops. If the plugin expects its timers to still fired in a nested event...

This appears to also hit file upload dialogs. From a recent Google search: > flash-plugin and nspluginwrapper have an interesting conflict where > file selection boxes used for flash upload...

Alright, we do have to support a recursive GTK event loop. Disassembling flashplayer suggests it calls gtk_dialog_run when it creates a GtkFileSelector. (Wasn't that been deprecated for GtkFileChooser forever ago.)...

One nuisance: what happens when the browser event loop isn't glib? Nested Xt event loops aren't worth supporting (if that's possible), but hopefully the world will move to NPN_PluginThreadAsyncCall. If...

To add to that a bit: AES and GHASH aren't very well-suited for fast, constant-time software implementations. But they're also ubiquitous so, in devices like phones, the hardware instructions really...

The thing with baselines is you only have one shot to get it right. If you require it later, it's not a baseline because there'll be devices in your ecosystem...

Oh that's fun. I hadn't realized there were two sets of them. It certainly would reduce the effort all around if there were fewer duplicate extensions (less copies of AES,...

In addition to issues with dynamic libraries, `atexit` is hazardous in multi-threaded applications. `atexit` runs when the main thread returns from `main`, but there's no guarantee that other threads have...

#17483 does not appear to address the threading issue, no. It is ultimately not safe for a thread-compatible library to use `atexit`. You need to know something about how the...