Question

Is there a limit on number of documents (tabs) that are concurrently open from LF web client?

Web Client Version 10 Web Customizations

Updated January 17, 2018

asked on January 15, 2018

One of our users experiences browser freeze after opening 5-th or 6-th document from web client concurrently. I tried that myself and I noticed that after opening numerous documents, at some point opening the next document either does not show the complete page or it shows a pop-up message from the webpage saying "Please configure your Popup Blocker to allow pop-ups from this site.", and my browser's Pop-up Blocker is turned Off.
Is there a limit to the number of documents concurrently open and if so, is it configurable?

If not, is the memory size causing this limitation?

Thanks

1 0

Answer

SELECTED ANSWER

replied on January 17, 2018

Hi Karineh, thanks for getting back to us.

We took another look, and we can reproduce the issue in IE on our internal environments. We find that IE becomes unresponsive with around 6-9 Doc Viewer tabs open.

I spoke to the lead Web Client developer regarding the issue. We suspect it may be caused by an inefficiency in IE, possibly a memory leak. Also, Chrome is known to put inactive tabs to sleep to conserve resources, and we suspect IE doesn't do this.

That said, we'll do some research to see if there's anything we can do on our side to fix the hangs that occur when multiple documents are open. In our research, it looks like IE is the only browser that has these slowdowns. Firefox Quantum, Chrome, and Edge all handled 8-9 open tabs smoothly.

In the meantime, your best bet is to switch browsers if that's possible in your organization, or inform/train users to avoid leaving multiple tabs open in IE.

0 0

Replies

replied on January 16, 2018

Hi there,

Web Client doesn't enforce any limit on number of documents users open client-side in their browser. I can open up 6-8 documents fine in chrome. I can't reproduce the pop-up behavior either so long as I set my pop-up blocker to off.

The browser slowdown could be caused by memory or CPU limitations. Which browser are you using? What does memory/cpu look like under task manager->Performance? If you press F12, are there any errors in the console?

0 0

View 1 previous reply

replied on January 17, 2018

Thank you so much for your response Ryan.

The default browser for our company is IE so that's what I and my user were using. I did try Chrome and it seems to handle it much better. I opened over 20 documents concurrently with no problems.

IE however seems to be hung because hitting F12 doesn't show anything. In some tabs it is stuck at "loading" and in some others where documents were already opened and displayed, parts of the screen is covered in black.
Hitting F12 in Chrome however brings up the debug view just fine.

Checking the CPU/Memory usage shows CPU around 15% and Memory around 58% on my system. I haven't checked my user's system though.

Thanks.

0 0

SELECTED ANSWER

replied on January 17, 2018

Hi Karineh, thanks for getting back to us.

We took another look, and we can reproduce the issue in IE on our internal environments. We find that IE becomes unresponsive with around 6-9 Doc Viewer tabs open.

In the meantime, your best bet is to switch browsers if that's possible in your organization, or inform/train users to avoid leaving multiple tabs open in IE.

0 0

replied on January 17, 2018

Hi Ryan,

Thanks for doing more investigation and your quick response.

We will do as you recommended and use Edge for now.

Should I mark your last comment as the answer or should we leave this open until further investigation?

Thanks.

0 0

replied on January 17, 2018

You can mark it answered for now, and we'll update the thread if there are any new findings.

0 0

You are not allowed to follow up in this post.

Question

Question

Is there a limit on number of documents (tabs) that are concurrently open from LF web client?

Answer

Replies

Sign in to reply to this post.