Quantcast
Channel: VMware Communities : All Content - VMware® ThinApp®
Viewing all articles
Browse latest Browse all 1382

Thinapp and browsers (Chrome and Firefox), lots of issues

$
0
0

Hello:

 

Are there some guidelines or best practices for capturing Chrome and Firefox?  The reason I am asking is that we are having a bunch of issues with each.  In more detail:

 

Chrome: We thinapped the latest version of Chrome, without any additional plugins, with and without the --no-sandbox option per the KB article here:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2104409VMware KB: Google Chrome fails when capturing Google Chrome with VMware ThinApp

This one works fine on the initial run, but after it is closed and opened a second time, it will not work properly after that.  It crashes, then upon re-launching it will consume 100% cpu and its window never opens even though the process is running.  If I clear the Thinapp sandbox folder for Chrome, it will open up fine for the first time, but when opening a second time the same issue comes back.

 

Firefox: We thinapped the latest version of Firefox, along with the latest Java 1.8.x, latest Flash, and VMware client integration plugin.  It worked fine for about a week then all of a sudden one day it no longer launches (and we haven't changed anything) with the error: Fatal Application Exit, Unable to Open.

 

I've been looking around and the information is fragmented.  I've seen posts with similar issues in the past but supposedly they were resolved with later versions of the Thinapp setup capture program which we are using the very latest and greatest version (5.1.1).  To my knowledge we are using best practices and using a bare minimum Windows 7 VM to capture with.  Any help would be appreciated, if there have been known working solutions or combinations of versions that work.

 

Thanks in advance.


Viewing all articles
Browse latest Browse all 1382

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>