Hi I am wondering if anybody is having issues using Google Chrome Embeded Browser. IE works just fine however switch anything over to Chrome it hangs up and I have to end process. Chrome is installed default location, running Windows 10 (insider preview)
Have you tried a web site like http://google.com?
Regards
David Hervieux
Yes same thing... However if I do External and not embedded all works as expected. I can just use that if it's a known issue or something. I just like the clean look of the tabs
Hello,
The embedded version of Chrome doesn't rely on your local installation of Google Chrome, it's a third party library, which means we don't have much control over it.
We weren't able to reproduce the issue on our end, but there is a new version of the library. We updated it and it will be available in the next build of RDM, it might fix your issue. If you still encounter the hang we'll diagnose further and get in contact with the third party developers.
Regards,
Hubert Mireault
Hubert, can you be more specific as to which build this new chrome library will be available in?
We have an active ticket with resource issues and the chrome library keeps being blamed as a significant contributing factor. We're running 13.6.5 right now.
Hello,
The update of the library should be available in 13.6.6.0.
I'm aware of the other ticket opened. This might fix the issue but I know of some improvements we could do for the performance which might also help. Those changes are hopefully going to be there for the one after that, 13.6.7.0, but we'll keep you updated on that.
Regards,
Hubert Mireault
sounds great. Right now its not a show stopper, but we're excited for the new library. Thanks for the update.
13.6.7 is out but I don't see anything in the release notes pertaining to Chrome Libraries. Any updates?
Hello,
Which part are you still encountering problems with? Is it the hanging or the resources? For the hang we updated the third party library in 13.6.6.0, but for the resources, what I had in mind doesn't work, so we're still looking as to what we can do.
Regards,
Hubert Mireault
I have had this very same issue for the lat 6 months.
Any embedded Chrome Browser session will, when opened, hang the entire application. My only course of action is to end task the RDM process.
I am running 14.1.3.0 64-bit
When selecting Firefox and opening the session, nothing happens. Maybe FireFox is required to be installed first?
When Select Internet Explorer the all sites in all Web Browser sessions will work, as much as IE allows some sites to work.
Can this be resolved soon please as IE is not the best browser type to be using these days.
Hello,
We've updated the third party for Chrome in our latest beta, RDM 2019.1.3.0, and it fixes a few issues we've previously had. Could you try it out and see if it fixes your problem?
Regards,
Hubert Mireault
I installed the latest beta 2019.1.3.0 but this did not make any difference.
Chrome Embedded still hangs the app completely.
Chrome External is fine.
FireFox embedded a white screen page appears and never loads the site, but does not hang.
Firefox external is fine
Internet Explorer embedded works.
Internet Explorer external works.
I did install over the top of my prod version, so perhaps it did not overwrite the necessary files? I could, when time allows, remove the app completely and install the beta again and see if this makes any difference. But I am doubtful.
Hello,
Instead of uninstalling/reinstalling you could download the ZIP version of RDM and test that way. As you said, though, I'm not convinced this would help.
For Chrome, could you try going in File > Options > Types > Web, and under the "Chrome" section, checking "disable run32dll usage". You can then restart RDM and see if Chrome still hangs. This changes the way the library is loaded, and for some workstations it might work better.
For Firefox itself it's trickier as updating the libraries will require more work than Chrome at the moment, since what we're using is quite old, as far as I know. This is in our todo list.
Regards,
Hubert Mireault
Ticking the option "disable run32dll usage" as you suggested worked for me, using the Beta. Would this also work on the Prod version, or will I have to wait for the Chrome Libraries change to be published on the Prod version first?
Yes, this should also work on the latest stable version (14.1.3.0). Some setups seem unable to use run32dll to load the Chrome embedded libraries. It was an issue on Windows 10 update 1809 among other things.
Regards,
Hubert Mireault