MediaMonkey COM Elevator issue since upgrade [#9306]

[nohitter151]

When will this be fixed???

It is hard to say, as it isn't entirely clear what the problem is. The reported issue is only reproducible for a subset of users so it isn't clear what is causing the elevated requests.

[jsibley]

First, could someone please manage user expectations (or at least, my expectations)? Should I expect to wait two weeks for a response from MM in this forum? Would there have been a response if someone else hadn't chimed in?

I'm willing to help troubleshoot, but it would help if the turnaround time were faster than 2 weeks.

I've used MM for years, but I'm getting increasingly frustrated by issues that aren't getting resolved and poor follow-up on support requests.

Thanks.

[Lowlander]

Did you send in a debug log (step 4b) to support capturing this issue (viewtopic.php?t=69)? When an issue isn't reproducible this is essential to getting it resolved. In this case it seems something very specific in the user environment is triggering this and what this is hasn't been discovered.

Secondly any resolution would be in MediaMonkey 4.1 which I would presume is still a little way out.

[nohitter151]

First, could someone please manage user expectations (or at least, my expectations)?

The forum is community driven. Yes, the MM team does read the forums, but if you want to be sure that they hear from you, you should open a support ticket.

[touriga]

Secondly any resolution would be in MediaMonkey 4.1 which I would presume is still a little way out.

Surely you have a bug severity level that warrants an interim patch/release? This bug would certainly qualify in my opinion. It effectively renders MM unusable unless you use it with privileges that leave your system prone to a security risk.

[robhere]

I am having the same issue and un-checking the OS integration box helped at start up. Now it happens when updating Podcast, maybe someone else can verify this.
maybe it will help.

[Lowlander]

Now it happens when updating Podcast

send in a debug log (step 4b) to support capturing this issue (viewtopic.php?t=69)

[nohitter151]

I am having the same issue and un-checking the OS integration box helped at start up. Now it happens when updating Podcast, maybe someone else can verify this.

Probably you have your podcasts downloaded to a location that requires elevated access. Check the download location at Options > Podcast.

[intelligo]

I'm having the COM elevator problem, too, but I've run MediaMonkey 4.0.6 Debug and would like to report the results. I have never run MM before installing MM 4.0.6 a few weeks ago.

Problem: After starting MediaMonkey (a. not as Administrator; b. with OS file integration disabled), MM runs for a several minutes appearing to a. continue download of queued podcasts; and b. rescanning my music directories. MM's responsiveness to any other command during this time is glacial. Then, MM starts throwing dozens of UAC permission requests for COM elevator, as has already been described. To escape MM, I have to kill it in Task Manager.

My configuration: i5 with up-to-date Windows 7 running on a laptop with 8 GB of memory. The music directories are on a lettered network drive referring to an external hard drive connected by USB 2 directly to my Netgear N600 router. File interactions with the network drive through Explorer are reasonably responsive, but with MM tend to be sluggish.

MM is configured per instructions for syncing via MM an iPod Touch with the latest updates to iOS. Syncing the iPod via MM seemed to have occurred successfully.

The latest version of iTunes is also installed, and is configured per instructions for syncing via MM an iPod Touch with the latest updates to iOS.

In an attempt to improve MM's responsiveness interacting with my network drive and possibly solve the COM elevator issue, I moved the MM database from its default location to the network drive, revising the INI file as instructed. No change in behaviour.

WINDOWS MESSAGES AND LOG OUTPUT FOLLOWS>>>>>

Code: Select all

MediaMonkey (Not Responding)

1) WINDOW: Thread creation error: Not enough storage is available to process this command.

2) WINDOW: There was a problem querying database.  Out of memory.

3) EurekaLog 6.0.21

Application:
-------------------------------------------------------
  1.1 Start Date      : Wed, 29 Aug 2012 20:20:43 -0400
  1.2 Name/Description: MediaMonkey.exe - (MediaMonke)
  1.3 Version Number  : 4.0.6.1501
  1.4 Parameters      :
  1.5 Compilation Date: Mon, 2 Jul 2012 16:28:43 -0400
  1.6 Up Time         : 1 hour, 38 minutes, 16 seconds

Exception:
-----------------------------------------------------------------------------------------------------
  2.1 Date          : Wed, 29 Aug 2012 21:58:59 -0400
  2.2 Address       : 75E2B9B7
  2.3 Module Name   : KERNELBASE.dll - (Windows NT BASE API Client DLL)
  2.4 Module Version: 6.1.7601.17651
  2.5 Type          : EThread
  2.6 Message       : Thread creation error: Not enough storage is available to process this command.
  2.7 ID            : 4046
  2.8 Count         : 1
  2.9 Status        : New
  2.10 Note         :

User:
-------------------------------------------------------
  3.1 ID        : decastro
  3.2 Name      : decastro
  3.3 Email     :
  3.4 Company   :
  3.5 Privileges: SeShutdownPrivilege             - OFF
                  SeChangeNotifyPrivilege         - ON
                  SeUndockPrivilege               - OFF
                  SeIncreaseWorkingSetPrivilege   - OFF
                  SeTimeZonePrivilege             - OFF

Active Controls:
---------------------------------------
  4.1 Form Class   : TFMainWindow
  4.2 Form Text    : MediaMonkey
  4.3 Control Class: TVirtualStringTree
  4.4 Control Text :

Computer:
-----------------------------------------------------------------------------------
  5.1 Name          : REYS-AXE
  5.2 Total Memory  : 8103 Mb
  5.3 Free Memory   : 4494 Mb
  5.4 Total Disk    : 673.64 Gb
  5.5 Free Disk     : 409.09 Gb
  5.6 System Up Time: 1 day, 4 hours, 43 minutes, 3 seconds
  5.7 Processor     : Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz
  5.8 Display Mode  : 1920 x 1080, 32 bit
  5.9 Display DPI   : 96
  5.10 Video Card   : Intel(R) HD Graphics 3000 (driver 8.15.10.2696 - RAM 2108 MB)
  5.11 Printer      : Canon MX870 series Printer (driver 2.37.2.10)

Operating System:
--------------------------------------------
  6.1 Type    : Microsoft Windows 7 (64 bit)
  6.2 Build # : 7601
  6.3 Update  : Service Pack 1
  6.4 Language: English
  6.5 Charset : 0

Network:
------------------
  7.1 IP Address:
  7.2 Submask   :
  7.3 Gateway   :
  7.4 DNS 1     :
  7.5 DNS 2     :
  7.6 DHCP      :

[Lowlander]

I'm having the COM elevator problem, too

send in a debug log (step 4b) to support capturing this issue (viewtopic.php?t=69)

[intelligo]

Roger, LowLander. Be back to you in a few.

[intelligo]

LowLander: I ran MM 4.0.6 Debug with the Microsoft debugger running and managed to get the COM elevator failure again.

Strangely, the MS debugger recorded nothing: empty log file.

I did, however, send multiple error reports that MM automatically generated. Where ever your company receives automated error reports from MM Debug, you will find a bunch of error reports from lucifer.yellow@gmail.com. Those are mine. Let me know if you have any trouble accessing them.

[Lowlander]

You may need to run DBGview as Administrator.

[intelligo]

Roger that, LowLander. I'm getting logging now. Be back to you in a few. Any luck finding my error reports?

[Lowlander]

The developers have access to user submitted AV logs from the program, not us users.