[TI] Chrome Victims

Discussion in 'General Archive' started by ŁÁĞÏ™, Jul 2, 2017.

Dear forum reader,

if you’d like to actively participate on the forum by joining discussions or starting your own threads or topics, please log into the game first. If you do not have a game account, you will need to register for one. We look forward to your next visit! CLICK HERE
  1. I have recently learnt of a problem which exists with chrome, some say "Chrome tries to stop flash player", some say, "It freezes once I have been on the backpage".

    I would like some people to come forward and explain in their words what the browser does when this happens, what are you doing before it happens, and if possible, can you post your system specs for me aswell, as all information given to me, will give me an idea of what to look for in attempts to solve this.

    This is opposed to someone just sitting on discord like "Its something with Chrome".

    Regards,

    LAGI.​
     
    Last edited: Jul 2, 2017
    ronz likes this.
  2. TheShadows

    TheShadows User

    I find that the game freezes when I open a new tab and switch back to the game when it is on the same window.

    However this problem is solved if you open the game on a separate window while keeping the back-page on another window. Then just avoid opening new tabs on the window that has the game running.
     
  3. @TheShadows, thanks for the reply, I too mentioned trying this to some people, for some it works, but for some it still causes a problem, I tried chrome when the problem was brought to my attention, having the game and backpage on the same window caused a slight pause between switching tabs, and like you say, bringing the game into its own window kind of makes it independent on its own, thus then not causing this pause or freeze. Some people still have the problem with or without the "independent window".

    With Firefox, the Flash Player plugin is made out-of-process, called PluginContainer.exe which runs as a process in task manager outside of FireFox itself, thus then causing it to run by its own means. With Chrome, you are now forced (because of their removal of support for NPAPI plugins) to use PepperFlash, which is built into the browser, which then in turn, runs within Chrome's processes.