Bug Report - Crash on Exit - Win98SE

[Girt]

I love this level editor - perfect balance of features and simplicity.
Even debugs it's issues - working great!

However, ever single time I exit, the program freezes, with this window:

An unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will be shut down immediately.

The process cannot access the file "C:\MISSIONEDITOR\M.EXE" because it is being used by another process.

DETAILS

System.IO>IOException: ...


Doesn't seem to affect a thing, but it could worry people...

- Girt

[scottlu]

Thanks girt. If you could, please post here the full text of the "details". We don't have a Win98 machine here but I may be able to see the problem by looking at the details. Thanks.

[Girt]

Details below. This happens no matter what level is open; mine, your samples, or none.



See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.IOException: The process cannot access the file "C:\MISSIONEDITOR\M.EXE" because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String str)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean useAsync, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode)
at m.MainForm.SaveSettings()
at m.MainForm.MainForm_Closing(Object sender, CancelEventArgs e)
at System.Windows.Forms.Form.OnClosing(CancelEventArgs e)
at System.Windows.Forms.Form.WmClose(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
mgui
Assembly Version: 1.0.1473.21739
Win32 Version: 1.0.1473.21739
CodeBase: file:///C:/MISSIONEDITOR/M.EXE
----------------------------------------
m
Assembly Version: 1.0.1473.21739
Win32 Version: 1.0.1473.21739
CodeBase: file:///C:/MISSIONEDITOR/m.DLL
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.






"We don't have a Win98 machine here but I may be able to see the problem by looking at the details. Thanks."

I tried XP but it didn't seem any more stable. It also dropped several features (why??) while adding some others. And I'm worried about much of my old software (like Palm stuff) not working on XP.
Laugh if you like, but note that the Virus community is longer fully supporting Win98 either.

Thanks for your debbugging!

[crakerz]

This looks like the same error report that occurs when you try to delete a unit from a Unit Group.

BTW, this is on XP Pro.