[fixed] deploy tool crashes on mpaudioswitcher.ax (2 Viewers)

[arion_p]

frankteb & kristerka:
In the log files from adplus I see that the following command line arguments are used:

[I](kristerka):
[/I]-crash -quiet -o c:\MP_crash_dumps -sc C:\WINDOWS\system32\regsvr32 C:\Program\Team MediaPortal\MediaPortal\MPAudioSwitcher.ax
[I](frankteb):
[/I]-crash -quiet -o c:\p_crash_dumps -sc C:\Windows\system32\regsvr32 C:\program files\team mediaportal\mediaportal\mpaudioswitcher.ax

It should have been (note the quotes around the pathname of MPAudioSwitcher):

[I](kristerka):
[/I]-crash -quiet -o c:\MP_crash_dumps -sc C:\WINDOWS\system32\regsvr32 [COLOR=Red]"[/COLOR]C:\Program\Team MediaPortal\MediaPortal\MPAudioSwitcher.ax[COLOR=Red]"[/COLOR]
[I](frankteb):
[/I]-crash -quiet -o c:\p_crash_dumps -sc C:\Windows\system32\regsvr32 [COLOR=Red]"[/COLOR]C:\program files\team mediaportal\mediaportal\mpaudioswitcher.ax[COLOR=Red]"[/COLOR]

Did you not use quotes, or did adplus just strip them in logs?

If you did not use quotes, it explains the different error (original crash is an Access Violation - 0xc0000005) because in fact regsvr32 ignores any part of the filename after the first space. If this is the case, please create new dumps using quotes around MPAudioSwitcher's pathname.

Thanks

 

[kristerka]

Yes i did, but to be sure her is a new.

Krister

 

[frankteb]

AW: deploy tool crashes on mpaudioswitcher.ax

Yes I used quotes. I will try it this nigth again.

 

[arion_p]

No need to try again (yet). I did some tests locally and I can confirm that adplus strips quotes. I am not sure if it strips them when logging (but uses them when launching regsvr32) or if it strips them altogether which would lead to a failure to register.

I did however notice that in the case of either successful registration or failed registration (but without crash), adplus produces crash dumps identical to those you posted. This means that in those tests regsvr32 completed successfully (it may still have failed to register the filter but it did not crash). Regsrv32 should have put out a message box stating the result of the registration process.

 

[cubii]

hi, is there a solution to this ? i just reactivated an olds laptop athlon 2500, with xp sp3 + updates and also getting this error...

Is the only solution to create an own installer with other mpaudioswitcher? (or wait for 1.2 final?)

cubii

 

[RAWPWR]

I'm wondering also. I like to install the beta, but it doesn't look like this issue is resolved. One would think that this should be top priority, on the list of BUGS....... but it's not. I'll just wait for the final release.

 

[mm1352000]

One would think that this should be top priority, on the list of BUGS....... but it's not. I'll just wait for the final release.

Not appreciated!
Trust me - this issue is causing *much* internal consternation. If we had news to report then you'd be the first to hear it here. This is *not* a straightforward problem though, so please give us the time we need to get to the bottom of what is going on.

mm

 

[RAWPWR]

Sorry... mm1352000, didn't mean to ruffle any-ones feathers. Thanks for the info. Much appreciated. Thank U Sir.... buddie.

 

[asselin]

I haven't encountered this problem, but figured I would try and help debug what's going on. I added logging to the startup code in the filter. If someone affected by this could try doing a regsvr32 on the attached module and posting the contents of MPAudioSwitcher.log (found in the standard Team MediaPortal\MediaPortal\log directory), it might narrow down what's happening.

FYI, the changes I made are
AudioSwitcher.cpp:

STDAPI DllRegisterServer()
{
	LogDebug("register 1");
	HRESULT res = AMovieDllRegisterServer2(TRUE);
	LogDebug("register 2");
	return res;
}

FilterApp.cpp:

BOOL CFilterApp::InitInstance()
{
	LogDebug("initinst 1");
	if(!__super::InitInstance())
		return FALSE;
	LogDebug("initinst 2");

	SetRegistryKey(_T("Gabest"));
	LogDebug("initinst 3");

	DllEntryPoint(AfxGetInstanceHandle(), DLL_PROCESS_ATTACH, 0);
	LogDebug("initinst 4");

	return TRUE;
}

BOOL CFilterApp::ExitInstance()
{
	LogDebug("exitinst 1");
	DllEntryPoint(AfxGetInstanceHandle(), DLL_PROCESS_DETACH, 0);
	LogDebug("exitinst 2");

	BOOL ret = __super::ExitInstance();
	LogDebug("exitinst 3");
   return ret;
}

Normal results would look something like this:

01-07-2011 23:52:38.955 [1d14]initinst 1
01-07-2011 23:52:38.961 [1d14]initinst 2
01-07-2011 23:52:38.964 [1d14]initinst 3
01-07-2011 23:52:38.966 [1d14]initinst 4
01-07-2011 23:52:38.969 [1d14]register 1
01-07-2011 23:52:38.981 [1d14]register 2
01-07-2011 23:52:40.084 [1d14]exitinst 1
01-07-2011 23:52:40.117 [1d14]exitinst 2
01-07-2011 23:52:40.121 [1d14]exitinst 3

 

[cheezey]

Here you go...


14-04-2004 00:13:15.218 [e00]initinst 1
14-04-2004 00:13:15.218 [e00]initinst 2
14-04-2004 00:13:15.218 [e00]initinst 3
14-04-2004 00:13:15.218 [e00]initinst 4
14-04-2004 00:13:15.218 [e00]register 1
14-04-2004 00:13:19.281 [e00]exitinst 1
14-04-2004 00:13:19.281 [e00]exitinst 2
14-04-2004 00:13:19.281 [e00]exitinst 3

(Ignore the date/time - this PC has been switched off for weeks and defaulted to a very old bios date.)