Hi

Look at this post: 

possobile reasons:

• more than five browser tabs
• page size larger than 240

Hi mate 

Sounds like there are similarities with our issue, but it was observed even when there is only a solitary tab open. We are on 25.1.1. which version is yours?

Cheers

You mentioned about 500 material lines so it fits to “page size larger than 240” or getting more rows manually on lines tab.

You have to apply U3 or U4 - do not remember.

We are experiencing the exact same issue. We have had a case open with IFS support for weeks (months really) and have not gotten any help. We have told our users to close the browser periodically and that helps, but the longer IFS runs, it will eventually cause the browser to just start locking up. We are on 24R2, 24.2.6

we experienced the same issue and reported a case to IFS. 

Is there any update on the ticket? Is this a bug in 25R1?

Thank you

case created today. No update yet.

But I think its a bug as I experienced the same issue for 2 customers after recent 25R1 deliveries .

BR,

Wasana

We have similar experience, but are on 24R2 still. Over a workday an IFS browser tab hogs memory and doesnt seem to release it back - some users in the end experience that chrome crashes with the IFS tab having more then 4GB allocated.

Any feedback on the case you created?

KR,

/Magnus
 

Hello Magnus,

We have upgraded CFG to 25R1 SU02 and are experiencing the same issues.

This was reported in SNOW case CS0437721 and IFS is delivering a fix for the issue to CFG this afternoon.
Will revert back tomorrow if this has solved the issue or not,

Br Hans

The fix is now applied in our CFG and it has solved the issue. Currently opened 10 tabs for CFG without issues.

Our SNOW case ref is CS0437721 for anyone who wants to request the same.

IFS made parameter changes on the application gateway side, 

Br Hans

Cheers. Do you mind sharing the IFS bug or patch id?

Hello athasanka,

I don’t have more details than the before mentioned case ID CS0437721 and the last update there:

“Corrective Actions:
• Database optimizations were performed to address the slowness.
• HTTP2 was enabled in the Azure Application Gateway settings.” 

Br Hans

hi, have you got a response to this from IFS? we are planning on doing SU5 on 25R1 and wondering if a patch might be included in it. Cheers

For a similar issue RnD has confirmed that the problem is occurring due to the use of an older version of the HTTP (1.1) protocol. They have recommended coordinating with the relevant team to verify the current HTTP version in use and update it to the latest version.

We’ve verified that we are on http 2, so there must be something else

in play.

This is a key user after working on a single tab for a couple of hours.