You are viewing limited content. For full access, please sign in.

Question

Question

Web Access 10 Crashing Browsers (Slow)

asked on February 8, 2016

We have installed installed LF 10 and also installed the newest patch. In Web Access we are using dynamic fields, with the max length set so that it is doing like a live search.

the database contains a few thousand rows, in the thick client there are no issues. 

In web access in both Chrome and IE the pages load fine and fast, but once you start entering data into the fields the whole thing grinds to a halt, and you don't even see what you type for a few seconds. the longer you have that session open the slower it gets, and then there will be long pauses were the browser wont even respond, or crash.

The single tab in chrome with one dynamic field being entered was up to 600MB of RAM usage.

Has anyone else had issues in WA 10 with what seems to me to be really slow javascript etc?  

0 0

Replies

replied on February 15, 2016

Hi Joel,

Thank you for reporting this issue. I've passed this along to our development team and they will look into fixing it in the upcoming hotfix. 

For your reference, the bug ID is 140360.

0 0
replied on February 15, 2016

Does this still happen without [Settings]MaxDropDownLength configured?

0 0
replied on February 18, 2016

If i turn off maxdrop down and it becomes a list it seems to perform fine. however of course its a huge list, which has its own issues.

0 0
replied on September 14, 2016

I was just testing this internally in response to an issue raised by a client. I have a template containing dynamic fields which are cached using [CacheFieldValues] and [MaxDropDownLength]. When I import a document via Web Access (10.1.1.248) the dynamic fields do not load at all - it just says "Loading..." and no data loads.

If I remove the [CacheFieldValues] attribute then the fields function as normal.

Are cached dynamic fields supposed to work in Web Access as they do in the client?

0 0
replied on September 14, 2016

We will look into getting this fixed (bug reference# 149047)

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.