[solved] MP 1.38 crashes with video play after updating from 1.37 to 1.38 (1 Viewer)

[ysmp]

Perhaps the problem is not in the Media Portal at all, but, for example, in LAV Filters, which requires new dependencies. Or in some Direct X, Sharp DX part of the libraries.

hi ajs,
i think you correct .... after update VC Redistr 2015-2022 all was working fine as normal.
but now have error in that was not before .... but still mp play o.k and wor as normal

[2025-07-29 12:30:59,220] [Error ] [MPMain ] [ERROR] - DirectShowUtil:RemoveFilter() - Exception COM object that has been separated from its underlying RCW cannot be used.

in: MediaPortal-Error (log folder)

but this fix in win 11 , what about win 7,10 .... users need to test and report.

 

[ajs]

DirectShowUtil:RemoveFilter() - Exception COM object that has been separated from its underlying RCW cannot be used.

Gemini say:

The error message "COM object that has been separated from its underlying RCW cannot be used" in the context of DirectShowUtil:RemoveFilter() indicates an issue with the lifetime management of a COM object within a .NET application utilizing DirectShow.

Explanation:

• COM Object:
  DirectShow is a COM-based technology, meaning its components (filters, graph managers, etc.) are implemented as COM objects.
• RCW (Runtime Callable Wrapper):
  When a .NET application interacts with a COM object, the .NET runtime creates an RCW. This RCW acts as a bridge, allowing .NET code to call methods on the COM object and vice-versa.
• Separation:
  The error "COM object that has been separated from its underlying RCW" means that the link between the .NET RCW and the underlying COM object has been broken. This typically happens when the COM object's lifetime has ended (e.g., it was released or uninitialized) while the RCW still exists and is being referenced by .NET code.
  

Common Causes in DirectShow:

• Premature Release:
  A COM object (like a filter) might be released or uninitialized by another part of the application or by the DirectShow graph itself, before DirectShowUtil:RemoveFilter() attempts to use its corresponding RCW.
• Threading Issues:
  If COM objects are created or released on different threads without proper synchronization, it can lead to situations where the RCW becomes invalid.
• Incorrect Object Management:
  Failing to properly manage the lifetime of DirectShow objects, such as not explicitly releasing interfaces when they are no longer needed, can lead to this error.
  

Troubleshooting Steps:

• Review Object Lifecycles:
  Carefully examine how DirectShow filters and other COM objects are created, used, and released within the application. Ensure that objects are not being released prematurely.
• Thread Safety:
  If multiple threads are interacting with DirectShow components, implement proper synchronization mechanisms (e.g., locks, mutexes) to ensure thread-safe access to COM objects.
• Explicit Release:
  Ensure that COM interfaces are explicitly released when no longer needed, typically by calling Marshal.ReleaseComObject() on the RCW or by allowing the garbage collector to handle it (though explicit release is often preferred for COM objects).
• Error Handling:
  Implement robust error handling around DirectShow operations to catch and manage potential issues related to COM object state.

@doskabouter Any ideas?

 

[ajs]

what about win 7,10 .... users need to test and report.

I have a HTPC on Windows 10 and 11, a combat one on 10, no problems (it was on it that I encountered this problem for the first time). 11 is a test one, there were no problems there right away.
It's high time to bury Windows 7 and upgrade to Windows 10 or 11.

 

[ysmp]

tks, ajs...
i think you better put a note and a link on mp1.38 new release.. to update the VC Redistr 2015-2022 when installing or updating versions to 1.38..
so users can know and save some time for them

tks
ysmp

 

[ajs]

to update the VC Redistr 2015-2022 when installing or updating versions to 1.38

This should be automatic, but in some cases it is clear that the installation is "silent" or the check does not give the desired result.

 

[ajs]

Most likely all versions of VC Redistr 2015-2022 have the same GUID, so the update does not occur automatically.

 

[ajs]

So far, according to statistics, there are about 800 downloads, and only 4 people have a problem, I think that’s not bad at all.

 

[Huowkutmas]

"Windows 7 x86" and Microsoft Visual C++ v14.44.35211.0
https://aka.ms/vs/17/release/vc_redist.x86.exe

No problem.

 

[2BitSculptor]

THANKYOU! for this solution. Works perfectly.

 

[CyberSimian]

So far, according to statistics, there are about 800 downloads, and only 4 people have a problem,

In addition to the test installs that I did previously (reported elsewhere), I have also done the following:

Upgrade install of 32-bit MP 1.38 over 32-bit MP 1.37 on 32-bit Windows 7
The install completed without error, and TV Server was fully operational. I have just tested the playing of videos, and there is no problem for me. MP works as normal. I should mention that all of my video files are recordings made by TV Server (TS files). I don't have any other types of video file to test.

I cannot test my Windows 10 installs at the moment as the test laptop is busy performing a long format of a large USB disk.

-- from CyberSimian in the UK