SAP GUI saplogon.exe process memory leak

[former_member656883]

Hello, this is our environment:

Kernel SAP : 721_EXT_REL

SAP GUI 7.30 on MS Windows 7 (90% clients)

SAP GUI 7.50 on MS Windows 7 (10% clients)

After about 5 years without major problems, around September 2019 the SAP GUI saplogon.exe process began to show massive memory leaks in some of our Windows 7 clients. Saplogon.exe process starts at under 100MB of memory used. Then, after some hours of use and memory eating, when the memory used by saplogon.exe reaches about 1.2GB, the SAP GUI starts to show a wide range of problems, from simple memory errors inside any transaction, to a sudden complete shutdown to the desktop of all the GUI windows, without any error message or log entry. It seems totally random and unrelated to the number or type of transactions active at the moment. Sometimes saplogon.exe, if left open with a couple of inactive transactions, starts to eat memory even at night time, while no one is actively using it. The next morning the user finds the saplogon.exe has reached the dreaded 1.2GB limit, all by itself. A couple clients have been upgraded from GUI 7.30 to 7.50 for the purpose of troubleshooting but with no results.

Before opening a ticket on the SAP support portal I wanted to know if someone may have had similar problems and if they found any solution that I, as a member of the IT team, may apply.

Thanks in advance.

[dasistdochscheisse]

Before you open a ticket at SAP, you should consider the following:

SAPGui 7.30 is out of maintenance, SAP would simply tell you to update SAPGui.

Check this link for the supportted combinations of Windows-Clients and SAPGui: https://www.sap.com/documents/2016/06/586c0458-767c-0010-82c7-eda71af511fa.html

-> Win 7: not supported at all
-> Win 10: preferred with SAPGui 7.60 but 7.50 is supported

[former_member656883]

Hi Ulf Brinkmeier, thank you for your reply.

Yes, I'm now aware that the OS/GUI combination we have in our environment is no longer supported. I updated the GUI to 7.50 in the problematic client, hoping that this might solve the problem, but unfortunately the situation has not changed.

[Sandra_Rossi]

Why 7.50 and not the latest one, 7.60?

[former_member656883]

Hi Sandra Rossi,

my plan was to try GUI 7.50 at first and then 7.60. In the process I actually started to think that the problem might not be the GUI version. Still, I intend to try 7.60 also, given that 7.50 brought no benefits.

[dasistdochscheisse]

If the SAPGui stays open all night and uses the memory, you could set "rdisp/gui_auto_logout" to a value of e.g. 7200 (i would set it higher than max_wprun_tiime). Thus, the user gets logged out after 2 hours. Next morning have a look at the memory consumption on the client.

This is an unusal bevaviour. Have you checked for malware on the client?

[former_member656883]

Today the SM04 is showing about half of the actual RAM consumed by the client.

Furthermore, I logged in with a different SAP user and the problem was exactly the same, even with this different user that is working well on other clients.

I am increasingly convinced that the culprit could be a corrupted Windows library, framework file or something similar used by the SAP GUI and that the GUI itself has no problems.

May be some Windows update installed damaged or incompatible system files that could not be restored to previous version when I uninstalled the recent updates.

I will try and use the SAP GUI from a different Windows user profile on the same client and see what happens.

[thorsten_kern]

Hello Alessandro, do you have some news on the memory problem? Do you have open a ticket in SAP?

I think i have the same problem in SAP GUI 7.4 and 7.6 on clients and desktop pc.

I display pictures in SAP GUI, each new picture increase the ram in windows. If the memory rise over 1 GB, then the GUI becomes unstable. When i close all transaktion, the ram is still reserved in Windows by > 1GB.

Regards,

Thorsten

[dave_utas3]

Hi Alessandro, any resolution on this? We have the same problem using 7.6 GUI, started beginning 2020 and only happens when we are in the HTML viewer doing an OCI (punchout to vendor) call - 1200mb then SAPGUI stops - all users.

[Sriram2009]

Hi Alessandro.

From the screen shot it clearing show that the memory consumed by desktop by task manager and SAP system for single GUI session. it is not process memory leak.

Regards

Sriram

[former_member656883]

Hi S Sriram,

Looking at the SM04 I can only tell that the amount of RAM consumed by the client is reported correctly (more or less) by the SAP system and by the client OS.

It is not clear though why the client uses so much RAM now?

Why it started using so much RAM since around september 2019, after years of work without problems?

Why other clients, using about the same transactions, do not use so much RAM?

In the very same screenshot you can see another client with 9 open sessions that uses less that 150MB RAM and other clients with 6 or 7 open session that even use less that 100MB RAM. Why the RAM usage in the subject client became so massively over the average since the last months?

[Sriram2009]

Hi Alessandro.

All are depending up the usage of SAP system it will be loaded in the both pleases, on SAP system you can check the user id over all memory usage in transaction code SM04. and in the local pc you task-manager over all usage of memory. if possible could you share the screen shot of both?

Regards

SS

[former_member656883]

Hi S Sriram,

Here are the screenshots from SM04 transaction and Windows task manager:

[script_man]

Hi Alessandro,

we had to make similar observations a few months ago. For a long time we suffered too. We were able to determine the locations of the memory increase, but nobody could help us. We did it ourselves.

We have the setting below

Help -> Settings -> F4 help-> System default switched to dialog (modal).

Since then there have been no problems with us. The only disadvantage is that this setting cannot be set centrally.

Regards,

ScriptMan

[former_member656883]

Hi Script Man, thank you for your reply.

I switched the F4 help option as per your suggestion, but unfortunately this did not resolve the problem.

[script_man]

Hi Alessandro,

did you closed saplogon.exe? Only then is it effective.

Regards, ScriptMan

[former_member656883]

Hi Script Man,

yes, I switched the option then rebooted the whole PC.

[Sriram2009]

Hi

1. what is the network bandwidth from client PC to SAP server?

2. Enable the SAP logon and Gui traces, check where you are getting loaded more, to my understand if the user is opening 8 / 10 session is over kill to SAP system. and also it may consumed more then 1 GB.

3. If possible inform user to use single session for an hour time, check the consumption of memory?

Regards

SS

[former_member656883]

Hi S Sriram,

1. The client is connected to the wired network through a 10/100 NIC and the throughput capacity is a steady 80Mbps on average. During normal client operations the actual network bandwidth used is less than 5% of the capacity.

2. I may agree that 8/10 sessions could be too many for the SAP system or the local RAM, but why it worked flawlessly for years then? And why it starts using only around 300/400Mb RAM for the first work hours then, at some point, suddenly it starts to constantly eat RAM until the 1.2Gb limit?

3. I will try and ask the user if he can work for one day limiting as much as possible the opening of multiple sessions and will see if this brings some benefits.

[kaus19d]

Hi alecontivalentini,

1st of all, raising a question thread in here SCN Forum is not opening ticket on SAP Support Portal. Here we discuss issues & try help each other. As you mentioned you are from the IT-support team in your organisation, I would recommend to engage your SAP-BASIS guy in this task & the SAP-BASIS guy can raise a OSS using your organisation S-User id

Coming back to you query,

There could be various reason for this like, corrupt SAP-GUI setup install, windows having corrupted setups installed. Did you try with a fresh SAP-GUI download from SAP Service Marketplace with using S-User details

Do you observe this issue on a Windows 10 fresh install system having SAP-GUI 7.50

Does the User has a custom SAP-scripts added to the SAP-GUI

Could you please check on the Event-Viewer log for the SAP-GUI & check if any details or error-code is written there for this

Could you also let us know what details do your SAP system have for the below SAP parameters,

rdisp/max_wprun_time

rdisp/gui_auto_logout

Thanks,

Kaushik

[former_member656883]

Hi Kaushik Debnath, thank you for your reply.

>Did you try with a fresh SAP-GUI download from SAP Service Marketplace with using S-User details

Yes. Latest 7.50 GUI download from the SAP Service Marketplace.

>Do you observe this issue on a Windows 10 fresh install system having SAP-GUI 7.50

Not exactly. I did observe this issue on Windows 10 but with GUI 7.30 patch level 8. Windows 10 client has not been upgraded to GUI 7.50 yet because upgrading did not resolve the problem on the Windows 7 client. I may try though.

>Does the User has a custom SAP-scripts added to the SAP-GUI

No custom scripts added to the SAPGUI.

>Could you please check on the Event-Viewer log for the SAP-GUI & check if any details or error-code is written there for this

Saplogon.exe related errors are loggend in the event log ONLY when the user forcibly closes the non responding GUI. In that case the generic event 1002 Application Hang is logged in the "Application" log, as for any other non responding application forcibly closed. Most of the times instead, when saplogon.exe reaches the 1.2GB limit, the whole SAPGUI closes down to desktop without any error message, while the system and other applications continue to work flawlessy.

>rdisp/max_wprun_time

Default value: 600

Profile value: 5400

Current value: 5400

>rdisp/gui_auto_logout

Default value: 0

Profile value: 0

Current value: 0

[kaus19d]

Hi alecontivalentini,

Based on your input, below would be my recomendation,

1st approach steps, set the below parameters,

rdisp/max_wprun_time=600(in DEFAULT.PFL),

rdisp/gui_auto_logout=600(in DEFAULT.PFL)

rdisp/keepalive=600(in DEFAULT.PFL)

Next approach steps,

Download a fresh Windows 7 professional setup from Microsoft portal(although there is a question for Windows 7 support from Microsoft) & install on a system or VM. Download SAPGUI 7.40 fresh & install & try

Download a fresh Windows 10 setup from Microsoft portal & install on a system or VM. Download SAPGUI 7.50 fresh & install & try

Thanks,

Kaushik

[Sriram2009]

Hi Alessandro.

1. What is the SAPGUI patch level in SAPGUI Version 7.30 & 7.50 ? and Windows 7 client security patches are updated with latest one?

2. On Windows 7 client during the peak time how many SAP session are opened? what was the overall load in the client system?

Regards

SS

[former_member656883]

Hi S Sriram, thank you for your reply.

1. SAPGUI was originally 7.30 patch level 8 when the problem started. I upgraded to 7.50 patch level 13 for the purpose of troubleshooting but without results. I did a normal uninstall-reboot-reinstall process, without deleting all the remaining files/folders that were referencing to previous installation. The Windows 7 client had all the latest updates and, given it had worked correctly for years, the first thing that came to mind was some recent update causing incompatibility. So, for the purpose of troubleshooting, I uninstalled all the updates up to 2 months before the problem started but, still, with no results.

2. During peak time the user has around 8/10 open SAP windows. The overall load on the client system is always well below 50% for CPU usage, RAM used by all processes and disk I/O. The client has 16GB RAM so in facts, even when the saplogon.exe reaches its 1.2GB limit, there are still over 10GB of free RAM in Windows.

[FrankKrauseGUI]

Hello Allessandro,

please use a current SAP GUI version (and not 7.30 or 7.50).
I am saying this, because there have been massive memory leaks in ALV Control and F4 Control that have been fixed

See SAP Notes 2821592 and 2787129.
If you can still reproduce the issues with a current patch, I recommend creating an incident.

Best regards,
Frank

[Sriram2009]

Hi Alessandro.

1. It is not clear though why the client uses so much RAM now?

To my view it is normal, if you are open any other client tool more then 6 sessions it will consumed that much resource on the desktop PC, for example you can open the 6 windows of internet explorer and check the memory consumption

2. Why it started using so much RAM since around september 2019, after years of work without problems?

You may not noted.

3. Why other clients, using about the same transactions, do not use so much RAM?

Other clients are opened 8 /10 sessions?

4. Looking at the SM04 I can only tell that the amount of RAM consumed by the client is reported correctly (more or less) by the SAP system and by the client OS.

Yes, In the SM04 one session only same way you can check 8 / 10 session in the SAP system it will show you more then 1 GB Ram.

Regards

Sriram

[dave_utas3]

Hi Alessandro, any resolution on this? We have the same issue in 2020 when making the OCI call - never happened in prior years and now get memory increasing to 1250 mb, and SAPGUI shuts down. We have never had SAP GUI shut down other than timeouts before. SAP Support has no answer for this.

[Sandra_Rossi]

Please reproduce the problem on a supported version of SAP GUI, then open a ticket at SAP support.

NB: I didn't find any SAP note which would tell how to troubleshoot memory leaks yourself.