After quitting the game DCS keeps running in the background occupying 1 cpu thread 100%

Rapierarch · April 9, 2022

After quitting the game DCS keeps running in the background occupying 1 cpu thread 100%. Only way to stop it is end task through the task manager.

Flappie · April 9, 2022

Please reproduce the issue, then attach your dcs.log file ("Saved Games/DCS.../Logs/dcs.log" - the file may appear as "dcs").

Rapierarch · April 12, 2022

here it is. It happened again. I did not know which file I needed to upload. I hope the correct one is included.

dcs.log debrief.log dcs.20220412-200524.dmp dcs.20220412-200524.crash

Flappie · April 12, 2022

Thanks. You did attach the file I was asking for (dcs.log), and I'm able to tell you you're having this issue. So far, I've not been able to determine what causes this.

We can see:

Alive vertex buffers: "1" instead of "0". That looks like the source of the problem.
The two "failed assert" errors at the end of the log,
No final "Log closed" message.

2022-04-12 21:25:52.450 INFO    APP: Screen: Mission
2022-04-12 21:25:55.913 INFO    APP: Screen: MainMenu
2022-04-12 21:25:59.506 INFO    EDCORE: (dDispatcher)enterToState_:5
2022-04-12 21:25:59.616 INFO    APP: application shutdown
2022-04-12 21:26:00.064 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 0
2022-04-12 21:26:00.066 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 1
2022-04-12 21:26:00.066 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 2
2022-04-12 21:26:00.152 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 3
2022-04-12 21:26:00.227 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 4
2022-04-12 21:26:00.235 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 5
2022-04-12 21:26:00.237 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 6
2022-04-12 21:26:00.238 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 7
2022-04-12 21:26:00.239 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 8
2022-04-12 21:26:00.241 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 9
2022-04-12 21:26:00.241 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 10
2022-04-12 21:26:00.242 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 11
2022-04-12 21:26:00.243 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 12
2022-04-12 21:26:00.243 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 13
2022-04-12 21:26:00.335 INFO    TERRAIN: lSystem::exit()
2022-04-12 21:26:00.335 INFO    VISUALIZER: TerrainRenderer::release
2022-04-12 21:26:00.335 INFO    TERRAIN: lSystem::CleanScenes()
2022-04-12 21:26:05.978 INFO    VISUALIZER: SceneManager_Implement::~SceneManager_Implement()
2022-04-12 21:26:05.981 INFO    VISUALIZER: TerrainRenderer::release
2022-04-12 21:26:06.150 WARNING LOG: 1 duplicate message(s) skipped.
2022-04-12 21:26:06.150 INFO    TERRAIN: lSystem::exit()
2022-04-12 21:26:06.150 INFO    TERRAIN: lSystem::CleanScenes()
2022-04-12 21:26:06.632 INFO    DX11BACKEND: DX11Renderer::shutdown()
2022-04-12 21:26:09.869 INFO    DX11BACKEND: NVIDIA API exit OK
2022-04-12 21:26:09.869 INFO    DX11BACKEND: textures_count: 0
2022-04-12 21:26:09.869 INFO    DX11BACKEND: textures_size: 0
2022-04-12 21:26:09.869 INFO    DX11BACKEND: buffers_count: 0
2022-04-12 21:26:09.869 INFO    DX11BACKEND: buffers_size: 0
2022-04-12 21:26:09.869 INFO    DX11BACKEND: CB_count: 0
2022-04-12 21:26:09.869 INFO    DX11BACKEND: CB_size: 0
2022-04-12 21:26:09.869 INFO    DX11BACKEND: SB_count: 0
2022-04-12 21:26:09.869 INFO    DX11BACKEND: SB_size: 0
2022-04-12 21:26:09.869 INFO    DX11BACKEND: IB_count: 0
2022-04-12 21:26:09.869 INFO    DX11BACKEND: IB_size: 0
2022-04-12 21:26:09.869 INFO    DX11BACKEND: VB_count: 0
2022-04-12 21:26:09.869 INFO    DX11BACKEND: VB_size: 0
2022-04-12 21:26:09.869 INFO    DX11BACKEND: total_buffers_size: 0
2022-04-12 21:26:09.869 INFO    DX11BACKEND: total_size: 0
2022-04-12 21:26:09.869 WARNING DX11BACKEND: alive vertex buffers: 1
2022-04-12 21:26:09.869 ERROR   DX11BACKEND: Failed assert `DX11VertexBuffer::buffersCount() == 0` at Projects\render\dx11backend_win8\Source\DX11Renderer.cpp:122
2022-04-12 21:26:09.869 WARNING DX11BACKEND: alive index buffers: 1
2022-04-12 21:26:09.869 ERROR   DX11BACKEND: Failed assert `DX11IndexBuffer::buffersCount() == 0` at Projects\render\dx11backend_win8\Source\DX11Renderer.cpp:123

Here's the end of my log file as a mean of comparison:

2022-04-12 21:34:52.848 INFO    APP: Screen: MainMenu
2022-04-12 21:34:54.928 INFO    EDCORE: (dDispatcher)enterToState_:5
2022-04-12 21:34:54.939 INFO    APP: application shutdown
2022-04-12 21:34:55.006 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 0
2022-04-12 21:34:55.010 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 1
2022-04-12 21:34:55.010 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 2
2022-04-12 21:34:55.176 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 3
2022-04-12 21:34:55.321 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 4
2022-04-12 21:34:55.336 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 5
2022-04-12 21:34:55.339 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 6
2022-04-12 21:34:55.344 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 7
2022-04-12 21:34:55.344 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 8
2022-04-12 21:34:55.349 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 9
2022-04-12 21:34:55.349 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 10
2022-04-12 21:34:55.351 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 11
2022-04-12 21:34:55.351 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 12
2022-04-12 21:34:55.351 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 13
2022-04-12 21:34:55.392 INFO    TERRAIN: lSystem::exit()
2022-04-12 21:34:55.392 INFO    VISUALIZER: TerrainRenderer::release
2022-04-12 21:34:55.392 INFO    TERRAIN: lSystem::CleanScenes()
2022-04-12 21:35:02.974 INFO    VISUALIZER: SceneManager_Implement::~SceneManager_Implement()
2022-04-12 21:35:02.975 INFO    VISUALIZER: TerrainRenderer::release
2022-04-12 21:35:02.992 WARNING LOG: 1 duplicate message(s) skipped.
2022-04-12 21:35:02.992 INFO    TERRAIN: lSystem::exit()
2022-04-12 21:35:02.992 INFO    TERRAIN: lSystem::CleanScenes()
2022-04-12 21:35:03.500 INFO    DX11BACKEND: DX11Renderer::shutdown()
2022-04-12 21:35:04.523 INFO    DX11BACKEND: NVIDIA API exit OK
2022-04-12 21:35:04.523 INFO    DX11BACKEND: textures_count: 0
2022-04-12 21:35:04.523 INFO    DX11BACKEND: textures_size: 0
2022-04-12 21:35:04.523 INFO    DX11BACKEND: buffers_count: 0
2022-04-12 21:35:04.523 INFO    DX11BACKEND: buffers_size: 0
2022-04-12 21:35:04.523 INFO    DX11BACKEND: CB_count: 0
2022-04-12 21:35:04.523 INFO    DX11BACKEND: CB_size: 0
2022-04-12 21:35:04.523 INFO    DX11BACKEND: SB_count: 0
2022-04-12 21:35:04.523 INFO    DX11BACKEND: SB_size: 0
2022-04-12 21:35:04.523 INFO    DX11BACKEND: IB_count: 0
2022-04-12 21:35:04.523 INFO    DX11BACKEND: IB_size: 0
2022-04-12 21:35:04.523 INFO    DX11BACKEND: VB_count: 0
2022-04-12 21:35:04.523 INFO    DX11BACKEND: VB_size: 0
2022-04-12 21:35:04.523 INFO    DX11BACKEND: total_buffers_size: 0
2022-04-12 21:35:04.523 INFO    DX11BACKEND: total_size: 0
=== Log closed.

Now, to the cause. Are you using an external app or some shader mod like ReShade?

Rapierarch · April 12, 2022

32 minutes ago, Flappie said:

Now, to the cause. Are you using an external app or some shader mod like ReShade?

No nothing at all. I only fly in VR (oculus q2). If it makes a sense for this.

Flappie · April 13, 2022

Ok. I saw the other user having this issue also uses VR. Maybe there's a link. Can you try without VR? That would be a good test to help the investigation.

At this point, I don't know what to do more to help you. You can open a support ticket (you need to log in on the DCS website, then go to Support, and Create a new ticket).

Rapierarch · April 13, 2022

29 minutes ago, Flappie said:

Can you try without VR?

It might sound silly may be but, I have never used DCS on flat screen. (I'm new only 1 year in DCS) so I have no means of headtracking, or I do not even have a free hat to look around and I believe I cannot fly anything on flat screen

I wanted to open a support ticket but I'm little bit confused there. It asks for a module where I have a problem with in the form. I do not know if this a moudule related issue so what should I fill there?

I'm actually at this moment trying to make Apache run in my system. 3950x 32GB 2070super. She does not fit to my VRAM. So I'm trying to lower every setting to bare minimum without turning the game in to garbage to get 36FPS from apache. So far I could not succeed. But the other user is having this far before Apache release. That's how I noticed this behavior from DCS.

When DCS exceeds VRAM it becomes a slide show. And most of the time I do not see the VRAM purged after exiting mission. So I had to exit game completely to free the VRAM.

Since task manager performance monitoring was running during my tests I noticed this high CPU load after quitting DCS.

Flappie · April 13, 2022

29 minutes ago, Rapierarch said:

It might sound silly may be but, I have never used DCS on flat screen. (I'm new only 1 year in DCS) so I have no means of headtracking, or I do not even have a free hat to look around and I believe I cannot fly anything on flat screen

It doesn't sound silly, it only makes me feel old! (I haven't tried VR yet)

29 minutes ago, Rapierarch said:

I wanted to open a support ticket but I'm little bit confused there. It asks for a module where I have a problem with in the form. I do not know if this a moudule related issue so what should I fill there?

Can you take a screenshot of what's blocking you? (hide your personal info if needed)

Here's an illustrated procedure to open a ticket:

Rapierarch · April 13, 2022

I have no problems getting there. My question was related to the following steps.

First I choose this after create a new ticket button,

Than what do I choose for the module. I do not think it is related to any module.

Flappie · April 13, 2022

I see. Then simply choose "Other question" and explain what is happening to you. Add in the link to the present thread.

Rapierarch · April 13, 2022

Ok! Wilco,

Thanks!

Rapierarch · April 26, 2022

Hi Flappie,

Support told me to increase the page file manually. I did not do that since I was always keeping an eye on the resources in the system DCS was nowhere close to eating up my memory. It was only killing my VRAM

Anyway I have remembered that I had HAGS in win10 turned on. I have disabled it and problem also disappeared. I never had it again for 2 weeks. I have also informed the support about it.

So you know what to do if someone else comes with the same problem.

Best regards,

Flappie · May 4, 2022

Many thanks, mate!

Flappie · October 9, 2022

OP says disabling HAGS actually did not solve the problem.

Sign In

After quitting the game DCS keeps running in the background occupying 1 cpu thread 100%

Recommended Posts

Rapierarch

Flappie

Rapierarch

Flappie

Rapierarch

Flappie

Rapierarch

Flappie

Rapierarch

Flappie

Rapierarch

Rapierarch

Flappie

Flappie

Recently Browsing 0 members