Forticlient causing Second Life Viewers to crash.

Forum|Forum|11 years ago
March 2, 2015
3 replies
5949 views

In the current development versions of Second Life and it's 3rd party viewer Firestorm, it has been noted that Forticlient has been the direct cause of a critical graphics error, involving HTTP Pipelining. This is an exclusive bug that can only be reproduced when Forticlient is used.

I would like to refer you to the Phoenix Firestorm Support JIRA: http://jira.phoenixviewer.com/browse/FIRE-15625

And the main Linden Lab Support JIRA (registration required): https://jira.secondlife.com/browse/BUG-8631

They contain more details, screenshots, and logs taken from both the Viewers and Forticlient. This has been reproduced by several members of the Firestorm support team with little in common between their systems other than Forticlient.

Second Life has roughly 40 million registered users, so even if only 1% use Forticlient the results would be unacceptable resulting in either a blocked release or users being informed to uninstall Forticlient, should they use it.

The developer of the HTTP Pipelining in the Linden Labs team is Monty Linden.

Note: I am only a user, I do not work for Linden Labs or Phoenix Firestorm, I am merely assisting the Firestorm Support Team on their behalf in this matter.

Eager to hear a response as soon as possible.

Best answer by kolawale_FTNT

Currently investigating, but will appreciate your help.

I have reviewed the report and discussions on both JIRA links. My current guess is that, with Second Life downloading textures and meshes over the internet, we may need to review how our Web Filtering feature handles traffic when HTTP Pipelining is in use. Please see what happens if you disable FortiClient Web Filtering (WF): does the issue still occur? Note: You can disable WF from the GUI. You may also try disabling FortiProxy on the File -> Settings page.

kolawale_FTNTAnswer

Staff

Currently investigating, but will appreciate your help.

I have reviewed the report and discussions on both JIRA links. My current guess is that, with Second Life downloading textures and meshes over the internet, we may need to review how our Web Filtering feature handles traffic when HTTP Pipelining is in use. Please see what happens if you disable FortiClient Web Filtering (WF): does the issue still occur? Note: You can disable WF from the GUI. You may also try disabling FortiProxy on the File -> Settings page.

smcfarlane8Author

New Member

kolawale_FTNT wrote:
Currently investigating, but will appreciate your help.

I have reviewed the report and discussions on both JIRA links. My current guess is that, with Second Life downloading textures and meshes over the internet, we may need to review how our Web Filtering feature handles traffic when HTTP Pipelining is in use. Please see what happens if you disable FortiClient Web Filtering (WF): does the issue still occur? Note: You can disable WF from the GUI. You may also try disabling FortiProxy on the File -> Settings page.

It worked. First attempt, I cleared the cache and ran again with Web Filtering disabled, same results as before. Second attempt, I cleared the cache again and disabled FortiProxy and all textures loaded fine. I will post the solution onto the support JIRA's, thank you so much for your help, hopefully a permanent solution will come in the future, but until then this will solve the issues users have experienced.

kolawale_FTNT

Staff

Will appreciate if you could retest with the recently released FortiClient 5.2.4. Keep all FortiClient features enabled, including Web Filtering.

Sign up

Login with SSO

Login to the community

Login with SSO