0012354: Smaller footprint and faster response from Windows integration

ID	Project	Category	View Status	Date Submitted	Last Update

0012354	MMW 5	Other	public	2014-11-12 23:54	2020-03-09 01:36

Reporter	peke	Assigned To
Priority	immediate	Severity	feature	Reproducibility	always
Status	closed	Resolution	fixed

Summary	0012354: Smaller footprint and faster response from Windows integration
Description	There is known issue where user double clicks on Track in Windows explorer. Windows starts MMW which in some cases AV active scan that scans mediamonkey.exe delays start of MMW up to a Minute along with playback start. Solution would be that we create small app (like we used to emulate winamp.exe) that will be parser to main MM app.
Additional Information	LAS-607-77836
Tags	No tags attached.

Fixed in build

peke 2017-02-03 23:03 developer ~0047177	This is still pressing issue for some users.

peke 2017-02-03 23:03 developer ~0047178	Raised priority for triage

peke 2017-02-05 23:54 developer ~0047188 Last edited: 2017-02-05 23:55	Strange is that on one PC I was able to reproduce but after integration cranges and few times MMW opened around 40 Seconds I could not replicate anymore. I asked user for more details and sent him my test result Video file.

peke 2017-02-28 17:05 developer ~0047380 Last edited: 2017-02-28 17:06	I'm not observing issue like with MM4.x When I manually set MM5 as Default app for playback. Are those changes that fixed MMW also applied to MM5?

petr 2017-03-04 15:14 developer ~0047397	MM5 have different architecture than MM4 (multi-process architecture).

peke 2020-03-09 01:36 developer ~0057119	Closing, Not being able to replicate by starting 2230 while watching both MM5 exe start and MS Defender Service CPU/Mem usage.