Memory, the CPU usage bug

[lunamoth]

v0.95.3 alpha build #10107 x64

Is a critical issue.

Memory, the CPU usage increases exponentially

Please fix it

[Wishmaster]

I cannot reproduce it. Could you use Process Explorer as described here?
And a versioninfo please:
here

[lunamoth]

1. process explorer
I'm not sure how it works, but I'll try.

2. version information

VersionInfo

CPU: Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz [Intel64 Family 6 Model 42 Stepping 7] [DEP enabled] [4 CPUs]
Installed RAM: 7967 MBytes
Operating System: Microsoft Windows 8.1 Edition, 64-bit  (build 9600)
Shell: explorer.exe
Internet Explorer: 9.11.9600.17207 (build 99600)
Administrator privileges: Yes
OS Languages: (UI | Locale (User/System)) : Korean/Korean | Korean/Korean
Free disk space on Miranda partition: 49182 MBytes

Miranda path: C:\lunamoth\-= UTIL =-\Miranda NG dev
Miranda NG version: 0.95.3 alpha build #10107 x64
Build time: 7 Aug 2014 11:55:17
Profile path: C:\lunamoth\-= UTIL =-\Miranda NG dev\Profiles\lunamoth\lunamoth.dat
Profile size: 1408.00 KBytes
Profile creation date: 13 Jun 2014 10:17:50
Language pack: No language pack installed
Service Mode: No

Active Plugins (19):
  AdvaImg.dll v.0.11.0.1 [7 Aug 2014 11:48:57] - Miranda image services
  AIM.dll v.0.11.0.1 [7 Aug 2014 11:48:11] - AIM protocol
  AVS.dll v.0.95.3.1 [7 Aug 2014 11:47:44] - Avatar service
  Clist_modern.dll v.0.9.1.1 [7 Aug 2014 11:50:32] - Modern contact list
  Cln_skinedit.dll v.0.0.0.4 [26 Jan 2014 20:07:38] - Skin editor for clist nicer
  Dbx_mmap.dll v.0.95.1.3 [7 Aug 2014 11:47:47] - Miranda NG mmap database driver
  Facebook.dll v.0.2.7.0 [7 Aug 2014 11:49:54] - Facebook RM
  GG.dll v.0.11.0.3 [7 Aug 2014 11:48:06] - Gadu-Gadu protocol
  ICQ.dll v.0.11.2.5 [7 Aug 2014 11:48:25] - IcqOscarJ protocol
  Import.dll v.0.11.0.1 [7 Aug 2014 11:47:45] - Import contacts and messages
  IRC.dll v.0.11.0.2 [7 Aug 2014 11:48:14] - IRC protocol
  Jabber.dll v.0.11.0.4 [7 Aug 2014 11:48:36] - Jabber protocol
  MSN.dll v.0.11.0.3 [7 Aug 2014 11:48:25] - MSN protocol
  PluginUpdater.dll v.0.1.2.2 [7 Aug 2014 11:51:45] - Plugin updater
  TabSRMM.dll v.3.4.0.2 [7 Aug 2014 11:48:06] - TabSRMM
  TopToolBar.dll v.0.8.0.3 [7 Aug 2014 11:50:14] - TopToolBar
  VersionInfo.dll v.1.5.0.3 [8 Aug 2014 5:50:08] - Version information
  WhatsApp.dll v.0.0.2.1 [15 Jan 2014 18:53:13] - WhatsApp Protocol
  Yahoo.dll v.0.11.0.1 [7 Aug 2014 11:48:16] - Yahoo protocol

[close]

[watcher]

lunamoth, we have a guide.
Post Merge: 08 08 2014, 07:30:32lunamoth,  WhatsApp.dll v.0.0.2.1 [15 Jan 2014 18:53:13] - WhatsApp Protocol

Update ASAP - http://wiki.miranda-ng.org/index.php?title=Plugin:WhatsApp/en

I Think this is what gives you the problem. WhatsApp should be updated manually - it's not in updater. When you download it there is a writing in red in WIKI "use at your own risk".

I'm almost sure that this is the reason for high CPU usage.

[lunamoth]

Wishmaster // FYI



ntoskrnl.exe!KeSynchronizeExecution+0x2246
ntoskrnl.exe!KeRemoveQueueEx+0x108e
ntoskrnl.exe!KeRemoveQueueEx+0xae9
ntoskrnl.exe!KeWaitForMultipleObjects+0x228
ntoskrnl.exe!ObWaitForMultipleObjects+0x289
ntoskrnl.exe!SeReleaseSecurityDescriptor+0x272
ntoskrnl.exe!setjmpex+0x34b3
ntdll.dll!ZwWaitForMultipleObjects+0xa
KERNELBASE.dll!WaitForMultipleObjectsEx+0xed
USER32.dll!MsgWaitForMultipleObjectsEx+0x13f
Miranda64.exe+0x15aa
Miranda64.exe!IcoLib_IsManaged+0x574e
KERNEL32.DLL!BaseThreadInitThunk+0xd
ntdll.dll!RtlUserThreadStart+0x1d


watcher // Thank you for your advice , I'll try.
Post Merge: 08 08 2014, 08:36:34disabled WhatsApp.dll , The problem still occurs

Process Explorer

ntoskrnl.exe!KeSynchronizeExecution+0x2246
ntoskrnl.exe!KeRemoveQueueEx+0x108e
ntoskrnl.exe!KeRemoveQueueEx+0xae9
ntoskrnl.exe!KeWaitForSingleObject+0x22a
ntoskrnl.exe!ExAcquireSharedStarveExclusive+0xc5e
ntoskrnl.exe!IoPageRead+0x49c
ntoskrnl.exe!ExReleasePushLockEx+0x445
ntoskrnl.exe!setjmpex+0x2057
MSVCR100.dll!memmove+0x2cf
MSVCR100.dll!memmove+0x2c5
facebook.dll+0x262e
facebook.dll+0xbb48
facebook.dll+0xc847
facebook.dll!Load+0x1d33a
facebook.dll!Load+0x87d9
facebook.dll!Load+0x8d0a
mir_core.dll!forkthread+0xee
MSVCR100.dll!endthreadex+0x43
MSVCR100.dll!endthreadex+0xdf
KERNEL32.DLL!BaseThreadInitThunk+0xd
ntdll.dll!RtlUserThreadStart+0x1d

facebook plugins bug??

[watcher]

lunamoth,  try to disable news notifications in Facebook - see if it helps
Post Merge: 08 08 2014, 08:58:09

Spoiler

[close]

[lunamoth]

watcher,

I really appreciate it. I'll try

[lunamoth]

The problem occurs again, I think facebook group chat problem.

Process Explorer Screenshot


Process Explorer stack
ntoskrnl.exe!KeSynchronizeExecution+0x2246
ntoskrnl.exe!KeRemoveQueueEx+0x108e
ntoskrnl.exe!KeRemoveQueueEx+0xae9
ntoskrnl.exe!KeWaitForMultipleObjects+0x228
ntoskrnl.exe!ObWaitForMultipleObjects+0x289
ntoskrnl.exe!SeReleaseSecurityDescriptor+0x272
ntoskrnl.exe!setjmpex+0x34b3
ntdll.dll!ZwWaitForMultipleObjects+0xa
KERNELBASE.dll!WaitForMultipleObjectsEx+0xed
USER32.dll!MsgWaitForMultipleObjectsEx+0x13f
Miranda64.exe+0x15aa
Miranda64.exe!IcoLib_IsManaged+0x574e
KERNEL32.DLL!BaseThreadInitThunk+0xd
ntdll.dll!RtlUserThreadStart+0x1d

[watcher]

Is this WinMain thread?

[Apollo2k4]

Is this WinMain thread?

Yes, but no symbols

[Robyer]

The problem occurs again, I think facebook group chat problem.

Ok, we can try that. I added hidden option for disabling chats (add in dbeditor to your fb account section new key "EnableChat", type Byte, with value 0). It will be in tomorrow's version. Then restart Miranda and it shouldn't show FB multi user chats at all. Then let me know whether it helped or not with your memory usage.

[lunamoth]

I disabled facebook plugin for a few days. It works fine.

I think the problem is Facebook Protocol Plugin (Facebook.dll v.0.2.7.0 [7 Aug 2014 11:49:54] - Facebook RM)

But, I'm not sure Steps to Reproduce, Cause of problem... I'm so sorry

[Robyer]

I disabled facebook plugin for a few days. It works fine.

Ok, so enable it again and disable group chats as I said in my previous post.

[lunamoth]

Robyer,

EnableChat = 0 Test Result

I use miranda ng few hours, it works fine, everything is normal