On some Windows systems there is a registry entry that stops the dll loader from loading from the current working directory (see http://support.microsoft.com/kb/2264107) This stops the chrome (29.0.1506.0) renderer processes from loading libpeerconnection.dll. --
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss