02501: All sets: Exiting mame sometimes results in having process "conime.exe" linger in memory

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
02501	Misc.	Minor	Sometimes	Oct 7, 2008, 18:28	Oct 8, 2008, 14:03

Tester	Iaspis	View Status	Public	Platform	MAME (Official Binary)
Assigned To		Resolution	Won't fix	OS	Windows XP/Vista 64-bit
Status [?]	Closed			Driver
Version	0.127u6	Fixed in Version		Build	Normal
		Fixed in Git Commit		Github Pull Request #

Summary	02501: All sets: Exiting mame sometimes results in having process "conime.exe" linger in memory
Description	When you exit mame sometimes there's an active process in memory called "conime.exe - Console IME" that seems to linger even after the termination of mame. I've found that it's somehow linked to console apps, It doesn't go away however and remains linked to mame.exe until you restart your system or manually remove it. This may be normal behaviour, I thought I should report it here though, just in case.
Steps To Reproduce
Additional Information
Github Commit

Flags
Regression Version
Affected Sets / Systems	All sets

Attached Files

No.02719 Tafoid Administrator Oct 8, 2008, 00:36	I have never seen this behavior on my install (Windows 2000). Doing some searching seems to indicate a couple possibilities: -A possible Virus/Backdoor is installed: http://www.file.net/process/conime.exe.html Determine where the .exe is located and sizes to see if there might be a problem there. -A Vista bug: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1097952&SiteID=1 http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1137631&SiteID=1 I'm quite sure this has nothing to do with MAME itself, but I'll leave it open for Feedback from Devs about this.
No.02720 Iaspis Tester Oct 8, 2008, 04:57 edited on: Oct 8, 2008, 05:01	Not a virus. It's a process that lauches upon running a console app (it does NOT launch with MameUI32/64) and apparently stays in memory afterwards. It's also linked to mame.exe so that you cannot move or remove it uless you reboot or kill the process. I tend to think it's a Vista bug. Just in case, I did a Virustotal check and it's clean (0 of 36).
No.02721 Fujix Administrator Oct 8, 2008, 14:03	This is a famous known work of Windows OS. Once it is triggered, it remains active. If it is not from a virus or something, no problem at all.