Sandboxie STEAM UAC mode (on windows 7) overloading cpu

[rrrr]

Steam still won't update under sandboxie. I also notice a old process from windows 10 activated and reduced everything for me:
http://imgur.com/UU4vwx5


this process is called "system and compress memory"

[6321678206]

Steam still won't update under sandboxie. I also notice a old process from windows 10 activated and reduced everything for me:
http://imgur.com/UU4vwx5


this process is called "system and compress memory"

http://superuser.com/questions/1032868/ ... uch-memory

[Barb@Invincea]

I am seeing mixed responses stating it works/doesn't work.

Which server region are you using for Steam? Can you try a different one and see if it helps?
Is this issue happening as soon as you launch the application, or when running a specific game?

Thank you.

[kawaiiwolf]

Hi barb, I just wanted to share with you some of the same problems I've been having with steam recently and how to reproduce them.

Operating Sytem: Windows 10x64 build 1607, fresh install with no additional software
Sandboxie: v5.14
Application: Steam, latest as of the time of this posting
Antivirus: No

I've installed a fresh copy of steam on a new box and a fresh copy of sandboxie. That's it other than windows itself (Note: Not running a nvidia GPU but the problem is the same on another computer I have with nvidia, old driverset).

- The first run of steam checks for updates. This process takes a moment before it opens, which is normal. Logging into an account and installing/playing a game is not necessary to demonstrate the error.

- Run steam again outside sandboxie, it opens right away, nice and perky. Close

- Run steam in sandboxie. It begins to utilize a lot of CPU as it attempts to check for, download and install updates. This process takes a minute or two. Close

- Run steam outside sandboxie. Still perky and fast. Close

- Run steam in sandboxie. Again, high CPU utilization and an attempt to update. Takes a minute or two and may be unresponsive.

This is in the North America region. So far it has nothing to do with running multiple instances or any specific game in general. I would be happy to help further debug if you have any instructions or things for me to try on my test box.

[Barb@Invincea]

Hello kawaiiwolf,

I am still unable to reproduce this issue, I do appreciate your detailed steps.

Are you updating Steam outside the Sandbox prior to running it? I got a 90% peak while updating Steam outside the Sandbox (but it lasted a few seconds) .
Once I am running it sandboxed, there are no peaks or issues (following your steps, I did not login, just launched it).

Also, if you could capture what's going on using procmon, that would be great:
https://live.sysinternals.com/Procmon.exe
That should ownload procmon.exe to your computer
Start procmon and reproduce the issue a few times, then save the log and upload it here.

Thanks,
Barb.-

[kawaiiwolf]

I went ahead and ran some experiments using steam and sandboxie. Fresh copy of windows 10 updated on build 1607. Fresh copy of sandboxie and steam and nothing else. Steam requires no login or games installed to witness the effects.

Default sandbox settings from a fresh install. Steam installed but never ran:
- First run of Steam outside sandbox (Steam updated, takes a couple minutes). Closed.
- Second run of Steam outside sandbox (Steam didn't require update). Closed.
- First run of Steam inside DefaultBox (Steam updated). Closed.
- Third run of Steam outside sandbox (Steam didn't require update). Closed.
- Second run of Steam inside DefaultBox (Steam updated). Closed.

It seems like steam is aware it's not in the right file location and attempts to redo the update each time. With a little tinkering:

- Opened Steam outside sandbox (Steam didn't require update). Closed.
- Deleted DefaultBox contents and set Direct File Access (OpenFilePath) in the sandbox settings to allow "C:\Program Files (x86)\Steam\", steam's default install location.
- Opened Steam outside sandbox (Steam didn't require update). Closed.
- Opened Steam inside sandbox (Steam updated). Closed.
- Opened Steam inside sandbox (Steam didn't require update, curious). Closed.
- Opened Steam inside sandbox (Steam didn't require update). Closed.
- Opened Steam outside sandbox (Steam updated). Closed.
- Opened Steam outside sandbox (Steam didn't require update). Closed.
- Opened Steam outside sandbox (Steam didn't require update). Closed.
- Opened Steam inside sandbox (Steam updated). Closed.
- Opened Steam inside sandbox (Steam didn't require update). Closed.
- Opened Steam inside sandbox (Steam didn't require update). Closed.

That seems to support that theory. So i tried to see if that was the same problem as installing into a sandbox.

- Uninstalled steam
- Emptied Default box but left Direct File Access (OpenFilePath) in the sandbox settings to allow "C:\Program Files (x86)\Steam\"
- Installed steam INSIDE the sandbox.
- Opened steam inside the sandbox (Steam updated as expected for a first run). Closed.
- Opened steam inside the sandbox (Steam took a very long time to open). Closed
- Opened steam inside the sandbox (Steam took a very long time to open). Closed

The procmon logs seem seems far more interesting, it spends nearly a minute or two of time trying to crate and access a "C:\logs\service_log.txt" file. This process was repeated but without the OpenFilePath set.

- Emptied Default box and restored default sandbox settings.
- Installed steam INSIDE the sandbox.
- Opened steam inside the sandbox (Steam updated as expected for a first run). Closed.
- Opened steam inside the sandbox (Steam took a very long time to open). Closed
- Opened steam inside the sandbox (Steam took a very long time to open). Closed

Same problem as above.

Procmon Logs have been passed on to Barb@Invincenta, but I suspect the temporary solution, for now, is to install steam outside a sandbox, set direct file access with OpenFilePath and run steam (and hence the games it calls) inside a sandbox.

[6321678206]

High CPU usage with csgo.exe this time since latest update just now... I found out which dll has the high CPU usage... I hope it's only a temporary issue at steam's end like last time...

[6321678206]

Even when I kill this dll with high CPU usage, there is still something causing abnormally high CPU usage and later this dll reactivates and CPU usage goes up again...

I think they really fixed something in the new update to prevent multiple CS:GO instances from working properly...

Even with 1 CS:GO instance sandboxed, CPU usage is over 50%...

EDIT:

Never mind, I found a workaround again...

[qwenzynnan]

hey 6321678206 how did u find a solution for csgo.exe solution.

i using w8.1 and my cpu usage is %60 even 1 game...

[6321678206]

Hey I think it's the new csgo update causing problems.

Even steamwebhelper.exe keeps crashing...

[Sayr]

Hey, Same problem with the new csgo update, before update 1 csgo take 7/8% CPU, and Now 17/18% so can't open many csgo

[Barb@Invincea]

Are these issues only happening when the application is Sandboxed? Are any downloads/updates involved?
Can you provide cpu usages for Steam + CSGO outside the sandbox?

Regards,
Barb.-

[oztskaan]

i use sandboxie 5.14 and 7 + 8 use steam and csgo last update in csgo i take still cant work 3+ more csgo and steam aps. i try use 4 use csgo cpu usege full. and i reset my pc. this problem last i think last uptade in csgo. i wait sandboxie dvlp fixed problem.

[Barb@Invincea]

i use sandboxie 5.14 and 7 + 8 use steam and csgo last update in csgo i take still cant work 3+ more csgo and steam aps. i try use 4 use csgo cpu usege full. and i reset my pc. this problem last i think last uptade in csgo. i wait sandboxie dvlp fixed problem.

You need to use the beta to play games properly (there was a problem with DirectX). Running multiple versions of the same program may, or may not work depending on the restrictions of said program. Sandboxie was not designed for that purpose.

Please compare cpu usage of Sandboxed Steam VS. non-sandboxed and provide the results.

Thank you.

[MexicanTroll]

The original problem was fixed but now it is not steam overloading the CPU its CS:GO app itself. 11% CPU usage per app.