Feeds / Search application using all of the ram

Anonymous

I noticed that the PC started running slow today and opened task manager to see that System, Feeds (Search application) is using CPU and Disk quite heavily and as much ram that it can to pin it to 100%.

Is anyone else experiencing this behavior?

Update: Windows crashed and i restarted, same application started to ramp up again so i ended it.

Looking into events now.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

308 answers

Anonymous

2022-04-30T17:37:17+00:00

Same problem, have all the latest updates installed. It can come randomly, this time it came while using YouTube and last time it came while the program BOINC used my processing power. The common thing with these programs seems to be that both uses the graphic card.

Computer specifications:

CPU: Intel Core i7 4771

RAM: 32,0GB Dubbel-Channel DDR3 (11-11-11-28)

Moderkort: ASRock Z87 Extreme6

Graphics: 4095MB NVIDIA GeForce GTX 1070

Antivirus: Bitdefender Total Security
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Anonymous

It is definitely a memory leak.

*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 131374

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 132621

    Key  : Analysis.Init.CPU.mSec
    Value: 577

    Key  : Analysis.Init.Elapsed.mSec
    Value: 41190

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 557

    Key  : Timeline.OS.Boot.DeltaSec
    Value: 874

    Key  : Timeline.Process.Start.DeltaSec
    Value: 552

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1

    Key  : WER.Process.Version
    Value: 10.0.19041.1682

FILE_IN_CAB:  SearchApp (4).DMP

NTGLOBALFLAG:  0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS:  0

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 0000000000000000
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD:  000012bc

PROCESS_NAME:  SearchApp.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_CODE_STR:  80000003

STACK_TEXT:  
00000026`a5b3f328 00007ffb`88eccbc0     : 00007ffb`8adaf338 00000000`00000000 0000012e`00000000 00007ffb`8ac07089 : ntdll!NtWaitForMultipleObjects+0x14
00000026`a5b3f330 00007ffb`80b37bb7     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`ffffffff : KERNELBASE!WaitForMultipleObjectsEx+0xf0
00000026`a5b3f620 00007ffb`80b37d9e     : 00000026`a5b3f9f0 00000000`00000000 00000026`a5b3f909 0000012e`ee428db0 : twinapi_appcore!Event::WaitWithFreeUnusedLibraries+0xd3
00000026`a5b3f8a0 00007ffb`80b37a24     : 00000000`00000000 00000000`00000000 00000000`00000000 0000012e`ee5054c0 : twinapi_appcore!<lambda_637730cb68025192ecc2dd05ba3ef033>::operator()+0x16a
00000026`a5b3f970 00007ffb`80b74172     : 00000000`00000002 0000012e`ee436c30 00000000`00000000 00000000`00000000 : twinapi_appcore!Windows::ApplicationModel::Core::CoreApplication::RunInternal+0x150
00000026`a5b3fb80 00007ffb`57a48af2     : 00000000`00000000 00000026`a5b3fbe8 0000012e`ee428db0 00000026`a5b3fbf8 : twinapi_appcore!Windows::ApplicationModel::Core::CoreApplicationFactory::Run+0x42
00000026`a5b3fbc0 00007ffb`57b84e4d     : 0000012e`ee4251e0 0000803a`87e82cf8 00000000`00000000 0000012e`ee5054c0 : Windows_UI_Xaml!RunInActivationMode+0xe6
00000026`a5b3fc30 00007ff6`29df243b     : 00000002`00000001 0000012e`ee424e50 00000000`00000002 0000012e`ee4251e0 : Windows_UI_Xaml!DirectUI::FrameworkApplicationFactory::Start+0x6d
00000026`a5b3fc80 00007ff6`29e47b9a     : 0000012e`ee424e50 00000000`0000000a 00000000`00000000 0000012e`ee424e50 : SearchApp!main+0x8b
00000026`a5b3fce0 00007ff6`29e46bf2     : 00000000`00000002 0000012e`ee424e50 0000012e`ee424ce0 00000000`00000000 : SearchApp!_main+0xa6
00000026`a5b3fd50 00007ffb`8afe7034     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : SearchApp!__scrt_common_main_seh+0x106
00000026`a5b3fd90 00007ffb`8b7c2651     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000026`a5b3fdc0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21

STACK_COMMAND:  ~0s; .ecxr ; kb

SYMBOL_NAME:  twinapi_appcore!Event::WaitWithFreeUnusedLibraries+d3

MODULE_NAME: twinapi_appcore

IMAGE_NAME:  twinapi.appcore.dll

FAILURE_BUCKET_ID:  BREAKPOINT_80000003_twinapi.appcore.dll!Event::WaitWithFreeUnusedLibraries

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  10.0.19041.964

FAILURE_ID_HASH:  {530b8f93-e816-5d78-42b5-a753ac3f6998}

Followup:     MachineOwner
---------

0 comments

Anonymous

2022-04-29T02:06:27+00:00

fixed it by ending task in task manager for the feeds app
Was this answer helpful?

0 comments No comments
Anonymous

2022-04-28T04:00:05+00:00

I wonder if the latest win updates from this Tuesday had anything to do with it on my end, it seems to have started a day after that. I know the problem happened long before that for some of you so might be something else with the news and interest feeds affecting people at random times.

So far its running ok again and I got my disc space on drive C: back also after killing news and interest. I never really used this feature anyways so will leave it off for now.
Was this answer helpful?

0 comments No comments