View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005181 | MMW v4 | Other | public | 2009-01-12 12:58 | 2009-02-23 01:35 |
Reporter | Assigned To | ||||
Priority | immediate | Severity | minor | Reproducibility | sometimes |
Status | closed | Resolution | fixed | ||
Product Version | 3.1 | ||||
Fixed in Version | 3.1 | ||||
Summary | 0005181: MM Stalls on startup while loading d_iphone.dll | ||||
Description | Intermittent problems reported by user with MM stalling on startup. Problem seems to vary between builds. 1209 got relatively solid. Debug log shows problems during load of d_iphone.dll. This appears to be a semi-known problem as I found other forum reports which recommended renaming / deleting the apple support dlls. | ||||
Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=35404&start=0&st=0&sk=t&sd=a | ||||
Tags | No tags attached. | ||||
Fixed in build | 1222 | ||||
|
MediaMonkey may freeze on some PCs that don't use/have an iPhone or iPod Touch and/or have a corrupted/invalid QuickTime installation or settings. as you pointed disabling the iPhone/Touch plugin usually solves the problem. The problem is not with MediaMonkey loading Plugin but with iTunes/QuickTime Shared libraries that are corrupted and locked while MM tries to load and use. As expected no error or any information is back to MM, actually DLL locks itself by loading other/additional (unknown to MM) shared libraries, where in some cases reinstalling of iTunes/QuickTime fixes the issue without renaming MM plugin. |
|
Setting as resolved(won't fix) and Assigned to Jiri for technical clarification. |
|
Would it be possible to either?: a)Have an option setting which enables/disables these plugins at runtime, or b)Have an option to not install the plugins. |
|
I don't know about any real solution for this problem, since it seems to happen during loading of Apple's dll and there isn't any known way how to detect that the problem will happen. Setting this to resolved, but we can reopen in case we succeed in finding some way how to detect possible problems. In order to do this, we should get detailed system information from every user having this issue, including Windows version, iTunes version and possibly some other things. |
|
I updated the issue in the forum. http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=35404&p=185613#p185613 |
|
What if you were to offer d_iphone.dll as a separate download available on the website as a downloadable plugin? I hate to think of all the potential users who download MM, it won't start up, and remove it straightaway because they can't figure out why it freezes on the splash screen. I guess the same could be said if users install MM and can't figure out why there iPhone or iTouch isn't detected, but its an idea. |
|
Yes, that has bugged me too (i.e. scaring away new users). What about a question when install MM. Something like: - Do you wish to install components so iPhone/iTouch can be synched with MM. Requires QuickTime/iTunes to be installed. |
|
Set to 'immediate' for the purposes of making an immediate decision. Since we're string frozen at this point, we can't rely on making any ui changes. |
|
Jiri, Maybe implementing Crash timer while loading risky DLLs would solve the issue? Crash timer would simply do Rename file rename and on next MM start MM could notify user that it has corrupted system component? Timer could work like this: 1. Risky DLL needs to be loaded 2. New self containing thread is created to check if DLL is Initialized correctly 3a. If Thread return Pointer to Mem location of loaded DLL then continue with MM loading 3b. If Timer wears off, MM will kill Created thread and rename offending DLL along with notifying user that it has corrupted system component 4. MM will proceed with loading |
|
Fixed in build 1222. - I moved the iPhone initialization code to a thread and it doesn't seem to have any negative side effect. I can't test whether it fixes that problem with MM freeze on startup, but we can ask the users having this problem to check it out. I wonder whether other QT related code works fine then, i.e. whether QT based m4a playback works well. |
|
I uninstalled Quicktime and ran MM, it started up without problems. In any case, verified that no regressions were introduced, build 1224 |