Full Version : Using xmlsave
xmlspawner >>XMLSpawner - Discussion >>Using xmlsave
<< Prev | Next >>
Novafire- 06-22-2006
Hi ArteGordon,
I'm running RunUO 2.0 with the latest Nerun distro v5.0 and your latest version of XmlSpawner. When I used xmlsave to save the spawns, my client crashed and a JIT pop up appeared.
Any idea what is the cause of the error?
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at Assistant.ClientCommunication.memcpy(Void* to, Void* from, Int32 len)
at Assistant.ClientCommunication.CopyToBuffer(Buffer* buffer, Byte* data, Int32 len)
at Assistant.ClientCommunication.HandleComm(Buffer* inBuff, Buffer* outBuff, Queue queue, PacketPath path)
at Assistant.ClientCommunication.OnRecv()
at Assistant.ClientCommunication.OnMessage(MainForm razor, UInt32 wParam, Int32 lParam)
at Assistant.MainForm.WndProc(Message& msg)
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
----------------------------------------
Razor
Assembly Version: 0.1.32.30195
Win32 Version: 0.1.32.30195
CodeBase: file:///C:/Program%20Files/Razor/Razor.exe
----------------------------------------
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
----------------------------------------
Ultima
Assembly Version: 1.0.2231.30459
Win32 Version: 1.0.2231.30459
CodeBase: file:///C:/Program%20Files/Razor/Ultima.DLL
----------------------------------------
RegexAssembly2_0
Assembly Version: 0.0.0.0
Win32 Version: n/a
CodeBase:
----------------------------------------
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
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.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.
[COLOR=blue][COLOR=blue][COLOR=blue]
ArteGordon- 06-22-2006
my guess is that it has something to do with the messages that are sent to the client during saves. Long strings can cause client crashes. I've tried to reduce the length of those messages to prevent that, but I will look into trimming them down even more.
Novafire- 06-22-2006
So that's what it was, kinda guessed it.
Anyway, it still saved the spawns ok. I reloaded the save file and it SEEMS ok. Same number of spawns saved/re-loaded, nice summary
It's a minor inconvenience I guess, with the client crashing out during the save.
ArteGordon- 06-22-2006

QUOTE (Novafire @ June 22, 2006 08:00 am)
So that's what it was, kinda guessed it. Anyway, it still saved the spawns ok. I reloaded the save file and it SEEMS ok. Same number of spawns saved/re-loaded, nice summary It's a minor inconvenience I guess, with the client crashing out during the save.

did you have the Journal open by any chance? Long strings in the journal will cause client crashes.
Having the client running or not wont have any impact on the save so even if it crashes, it wont affect anything on the server side.
Novafire- 06-23-2006

QUOTE (ArteGordon @ June 22, 2006 01:19 pm)

QUOTE (Novafire @ June 22, 2006 08:00 am)
So that's what it was, kinda guessed it. Anyway, it still saved the spawns ok. I reloaded the save file and it SEEMS ok. Same number of spawns saved/re-loaded, nice summary It's a minor inconvenience I guess, with the client crashing out during the save.

did you have the Journal open by any chance? Long strings in the journal will cause client crashes.
Having the client running or not wont have any impact on the save so even if it crashes, it wont affect anything on the server side.
Yes I did have the journal opened. I'll keep that in mind next time.
Thanks.