Skip to content

EarTrumpet using around 20-30% of 12700k clocked at stock #1648

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Samdune opened this issue Dec 12, 2024 · 10 comments
Closed

EarTrumpet using around 20-30% of 12700k clocked at stock #1648

Samdune opened this issue Dec 12, 2024 · 10 comments

Comments

@Samdune
Copy link

Samdune commented Dec 12, 2024

Summary

See title

Steps to reproduce

It's mostly constant, but sometimes goes down to normal usage.

EarTrumpet version

2.3.0.0

Windows version

10.0.22621.2283

Additional information

I have a dump file, but it's >600 MB, so can't upload it here.
I've uploaded it to Mega, see link below:
https://mega.nz/file/d4QX1LDL#k88NhLVsFGM6U6aNuzjpoBt-CVRIs_6efaKnft51HDE

@riverar
Copy link
Contributor

riverar commented Dec 12, 2024

Thanks, I downloaded it. You can delete the dump just in case it has sensitive information.

@riverar
Copy link
Contributor

riverar commented Dec 12, 2024

Can you also zip up the C:\Windows\Microsoft.NET\Framework\v4.0.30319 folder? .NET Framework process dumps need some files that need to match your OS. Thanks!

@Samdune
Copy link
Author

Samdune commented Dec 12, 2024

@riverar
Copy link
Contributor

riverar commented Dec 13, 2024

Ah right, I always forget EarTrumpet is 32-bit and to create usable dumps, you have to use the 32-bit copy of Task Manager (C:\Windows\SysWOW64\Taskmgr.exe). If you see it eat CPU again, can you capture a new dump?

(Alternatively, you could switch to a dev build which uses much newer .NET, WPF, etc.)

(I think I'll add a "Create dump" button in the app as well.)

@Samdune
Copy link
Author

Samdune commented Dec 13, 2024

https://mega.nz/file/1gBQVYLY#TcHMkM-7ws4TVux_WLgCqmNiN75pNVfH2DYOeFtuQwQ
Saw it hitting 50% briefly, then back down to 20-30% consistently.

@riverar
Copy link
Contributor

riverar commented Dec 13, 2024

That was fast, thanks! Checking.

@riverar
Copy link
Contributor

riverar commented Dec 13, 2024

0:000> !runaway
 User Mode Time
  Thread       Time
    0:6d28     0 days 0:03:29.140
    7:73bc     0 days 0:03:16.937
    5:6e10     0 days 0:00:04.109
    4:6e08     0 days 0:00:01.000
[...]

0:000> ~7k
 # ChildEBP RetAddr      
00 056ffbdc 76dcffd9     ucrtbase!__ascii_wcsicmp+0x10
01 056ffc18 76dcffa5     ucrtbase!__crt_state_management::wrapped_invoke<int (__cdecl*)(wchar_t const *,wchar_t const *),wchar_t const *,wchar_t const *,int>+0x2b
02 056ffc24 65ddbc40     ucrtbase!_o__wcsicmp+0x15
03 056ffc80 65ddbb57     AudioSes!CAudioSessionControl::OnAudioSessionEvent+0xd0
04 056ffc8c 65f4517b     AudioSes!CAudioSessionControl::CAudioSessionNotificationDelegator::OnMediaNotification+0x17
05 056ffcec 65f44f4e     MMDevAPI!CMediaNotifications::OnMediaNotificationWorkerHandler+0x21b
06 056ffcf8 776ce47c     MMDevAPI!CMediaNotifications::MediaNotificationWorkerHandler+0xe
07 056ffd1c 7769eb73     ntdll!TppSimplepExecuteCallback+0x7c
08 056ffed8 75dd7ba9     ntdll!TppWorkerThread+0x733
09 056ffee8 776cb79b     kernel32!BaseThreadInitThunk+0x19
0a 056fff40 776cb71f     ntdll!__RtlUserThreadStart+0x2b
0b 056fff50 00000000     ntdll!_RtlUserThreadStart+0x1b

Looks like the Windows audio stack is getting hammered. Are frequent audio session changes occurring on your system? (e.g., apps starting/stopping, constant volume changes, some other audio applications running, etc.)

@riverar
Copy link
Contributor

riverar commented Dec 13, 2024

Specifically, looks like the System Sounds session might be hamming us with notifications.

Example:

15:49:01.384 64   AudioDeviceSession OnStateChanged Active *SystemSounds {...}
15:49:01.384 64   AudioDeviceSession OnStateChanged Active *SystemSounds {...}
15:49:01.384 73   AudioDeviceSessionCollection OnSessionCreated
15:49:01.384 18   AudioDeviceSessionCollection OnSessionCreated
15:49:01.384 64   AudioDeviceSession OnStateChanged Active *SystemSounds {...}
15:49:01.384 64   AudioDeviceSession OnStateChanged Active *SystemSounds {...}
15:49:01.384 93   AudioDeviceSessionCollection OnSessionCreated
15:49:01.384 67   AudioDeviceSessionCollection OnSessionCreated
15:49:01.384 64   AudioDeviceSession OnStateChanged Active *SystemSounds {...}
15:49:01.384 73   AudioDeviceSessionCollection CreateAndAddSession System.Runtime.InteropServices.COMException (0x88890004)
15:49:01.384 64   AudioDeviceSession OnStateChanged Active *SystemSounds {...}
15:49:01.384 18   AudioDeviceSessionCollection CreateAndAddSession System.Runtime.InteropServices.COMException (0x88890004)
15:49:01.385 93   AudioDeviceSessionCollection CreateAndAddSession System.Runtime.InteropServices.COMException (0x88890004)
15:49:01.385 73   AudioDeviceSessionCollection OnSessionCreated
15:49:01.385 64   AudioDeviceSession OnStateChanged Active *SystemSounds {...}
15:49:01.385 67   AudioDeviceSessionCollection CreateAndAddSession System.Runtime.InteropServices.COMException (0x88890004)
15:49:01.385 64   AudioDeviceSession OnStateChanged Active *SystemSounds {...}
15:49:01.385 64   AudioDeviceSession OnStateChanged Active *SystemSounds {...}
15:49:01.385 73   AudioDeviceSessionCollection CreateAndAddSession System.Runtime.InteropServices.COMException (0x88890004)
15:49:01.385 64   AudioDeviceSession OnStateChanged Active *SystemSounds {...}
15:49:01.385 64   AudioDeviceSession OnStateChanged Active *SystemSounds {...}
15:49:01.385 64   AudioDeviceSession OnStateChanged Active *SystemSounds {...}
15:49:01.385 93   AudioDeviceSessionCollection OnSessionCreated
15:49:01.385 64   AudioDeviceSession OnStateChanged Active *SystemSounds {...}

@Samdune
Copy link
Author

Samdune commented Dec 13, 2024

Looks like it might be a program called Soundswitch causing it. I haven't seen the usage spike since disabling it.
Thanks for the help!

@riverar
Copy link
Contributor

riverar commented Dec 24, 2024

Thanks, closing for now but will associate with #1305

@riverar riverar closed this as completed Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants