This forum is archived and no longer active. You can visit us in our Discord Server here!

Topic: Critical issue with Fantasy Cruncher and Chrome ver. 59 (June 2017)

1

There is an issue with Chrome version 59 that affects a core function the way FC currently executes. Without getting too technical, the calculation of lineups runs in a separate process on each users computer, allowing the continued use of FC while the calculations are happening. In Chrome v 59 this background process keeps terminating prematurely resulting in the message that only X lineups can be calculated. This number varies from calculation to calculation (without changing anything) and is seemingly random at this point. If you calculate a few lineups, then use the calculate more lineups button, you will see the calculation will continue because the background process is then restarted.

We are working on determining the exact cause now, and will get a fix out asap, but I do not have an ETA at the moment. This is obviously a critical issue and we are treating it as such. In the meantime, IF YOU HAVE NOT UPDATED CHROME, PLEASE WAIT A FEW DAYS. If you have already updated and are experiencing this issue, your best options are to either use Firefox for the next few days, or you can download the previous version of Chrome (ver 58) from the following links. You would need to uninstall your current version and re-install the appropriate one.

Chrome 64 bit Windows
https://dl.google.com/tag/s/appguid%3D%7B8A69D345-D564-463C-AFF1-A69D9E530F96%7D%26iid%3D%7B441B2A72-75A4-3DD0-34BE-5F472CC2CFCD%7D%26lang%3Den%26browser%3D3%26usagestats%3D0%26appname%3DGoogle%2520Chrome%26needsadmin%3Dprefers/update2/installers/ChromeStandaloneSetup.exe

Chrome 32 bit Windows
https://dl.google.com/tag/s/appguid%3D%7B8A69D345-D564-463C-AFF1-A69D9E530F96%7D%26iid%3D%7B441B2A72-75A4-3DD0-34BE-5F472CC2CFCD%7D%26lang%3Den%26browser%3D3%26usagestats%3D0%26appname%3DGoogle%2520Chrome%26needsadmin%3Dprefers/update2/installers/ChromeStandaloneSetup.exe

Thanks for the heads up

how long before this will be fixed with ver 59

GOOD NEWS!

The bug was isolated and reported to the Chrome dev team last week where they accepted and corrected the bug. It looks like the fix is included in the newest version which I just tested and everything seems to be back to normal. You should be able to update now with no issues.

[color=red]BAD version:[/color] 59.0.3071.86

[color=green]Good Version:[/color] 59.0.3071.109