Announcements

Between mid-October and November, the content on AREA will be relocated to the Autodesk Community M&E Hub and the Autodesk Community Gallery. Learn more HERE.

QtWebEngineProcess.exe RAM hog 97% usage of 32GB

QtWebEngineProcess.exe RAM hog 97% usage of 32GB

Anonymous
Not applicable
20,664 Views
30 Replies
Message 1 of 31

QtWebEngineProcess.exe RAM hog 97% usage of 32GB

Anonymous
Not applicable

So, i just finished up watching an Amazon Prime movie, FYI this is like... the 6th movie i've watched through Chrome, however...

This is the FIRST one i've watched since installing 3DS Max 2020... it was Star Trek: First Contact... don't judge.

just as Picard is saying his goodbye to Lily, to beam back to the Enterprise-E i noticed a stutter, at first i didn't think much about it, my internet isn't the greatest so i figured buffering lag.

Credits roll, and i go to minimize and then close the movie, when i notice the cursor stuttering too... ok, thats system side... oh boy whats going on... 

Bringing up task manager which i keep running in the background and notice RAM has been pegged for a while and i notice HDD starting to peg too... wtf??

go to "Processes" to then sort by "Memory" and find a program called "QtWebEngineProcess.exe" is hogging all the RAM for some odd reason... i wasn't doing anything other than watching an Amazon Prime video...

ok, this thing looks new to me so i do some sleuthing first before i *end task* it, cuz once it goes poof i'll never find it on my own.

Right Click - Open Folder Location: "C:\Program Files\Autodesk\3ds Max 2020" wait what? i haven't even booted that program since last night!

seeing 27 files all starting with "Qt" its clearly not some kind of coincidence, its part of the program... ok, google search to the rescue?

first dozen or so results about "QtWebEngineProcess.exe" say its a malware, and used by more than one program, like Origin by EA for example...

 

I'm more than certain, 3DS Max 2020 isn't malware... though it does seem like it has malicious tendencies towards ones sanity when modeling... but that's more operator error and general program instability imo.

 

so...

why the hell is it running without any other 3DS Max program running? and why is it consuming all that RAM???

QtWebEngineProcess.JPG

0 Likes
Accepted solutions (1)
20,665 Views
30 Replies
Replies (30)
Message 21 of 31

jon.bell
Alumni
Alumni
Accepted solution

Hi @Anonymous @buzzB97XQ ,

 

Have you tried this with 3ds Max 2021? I know that we addressed some Qt issues in the 2021 version, so I'm curious if you're still seeing this if you use 2021. Could you please let me know? Thanks!



Jon A. Bell
Senior Technical Support Specialist, 3ds Max
0 Likes
Message 22 of 31

lodonoghue6FZGW
Explorer
Explorer
Hi
We haven't upgraded to 2021 yet, we will likely wait for the next vray version and upgrade in 1 hit. For me the problem isn't that frequent, which sort of makes it frustrating when it does crop up!
Message 23 of 31

Anonymous
Not applicable

we users will never use the newest versions of 3ds max, understand already, vray, corona and others do not adapt so quickly to new versions, I think you should fix problems in the past versions of your product, not only in the newest ..

0 Likes
Message 24 of 31

jon.bell
Alumni
Alumni

Hi @Anonymous,

 

Many of our users do upgrade to the latest versions of 3ds Max when they're released.

 

V-Ray 5 for 3ds Max 2021 was available almost immediately after 2021 was released, along with quite a few of our other biggest plugins.

 

In addition, we're not even sure that all these incidents are related to 3ds Max, especially if the original user hadn't opened Max or had Max running when the process starting eating RAM. Everything from the Origin game launcher to DropBox uses the Qt web engine and could be the culprit.

 

Regardless, if anyone here sees this issue happening with 3ds Max 2021 specifically, please contact me and let me know. Thanks!



Jon A. Bell
Senior Technical Support Specialist, 3ds Max
Message 25 of 31

jon.bell
Alumni
Alumni

@Anonymous ,

 

Just checking back with you to see if you'd upgraded to 3ds Max 2021 and if you (or anyone else here on this thread) was still seeing these Qt issues.

 

Please let us know, and we hope to hear from you soon!



Jon A. Bell
Senior Technical Support Specialist, 3ds Max
Message 26 of 31

Anonymous
Not applicable

any effected solution for this problem (  QtWebEngineProcess ) stop working in 3dsmax 2022 and viewport not responding in 3ds max  2022 start-up 

0 Likes
Message 27 of 31

Anonymous
Not applicable

This problem is still relevant. I ran into this problem today. 9 GB of RAM eats up this file

0 Likes
Message 28 of 31

Anonymous
Not applicable

Well this process outright crashes 3dsmax 2022 on windows 11. sucks.

0 Likes
Message 29 of 31

DanielCantin
Autodesk
Autodesk

Hi @Anonymous 

 

Can you give use more details in which conditions this crash happen on Windows 11 (reproduction steps)?
Was there a crash report associated with the crash, if yes, can  you give us the report ID?

 

Thanks for reporting the issue.



Daniel Cantin
QA Manager, 3ds Max, Maya
Entertainment Creation Products, ECP
0 Likes
Message 30 of 31

syndicate5
Enthusiast
Enthusiast

This is an issue if you have Vray installed, maybe specifically Vray GPU. BTW, someone mentioned also high CPU usage. Yes, this can cause high CPU usage so no one is "fabricating issues here" as someone mentioned. I only get this issue when using Vray6. Never had an issue with 5 or lower. Most of us cant afford to upgrade to a newer version of Max so this is a real bummer.

https://www.instagram.com/the_3rdkind
0 Likes
Message 31 of 31

lodonoghue6FZGW
Explorer
Explorer

Hi Jon

 

Firstly, we moved to 2022 a while ago and the problems have gone. I should have updated my post earlier, apologies.

 

We didn't try 2021, as we moved from 2020 straight to 2022. We use Vray Next and Vray GPU. We have also shifted from Windows 7 to a mix of Windows 10 and 11

 

The specific machine (windows 7, max 2020) that most frequently had the problem is no longer in circulation. We were never able to solve the 2020 problem on it, no updates made any difference. We simply kept an eye on the memory usage and killed the process periodically. I suspect, as you suggest, that max might not have been the culprit alone (although we never saw it unles max had been used). My money is on more than one application using the same process and them not playing nicely together

 

Its all moot for us however, the problem doesn't exist (for us) in 2022 in windows 10-11 and with vray

0 Likes