Reading HTML message
Brought to you by:
albinsunnanbo
Menu
▾
▴
#64 Reading HTML message
Unhandled Thread exception
Kom version: 0.9.0.932
System.Environment.OSVersion = Microsoft Windows NT 6.0.6001 Service Pack 1
System.OutOfMemoryException: Ett undantagsfel av typen System.OutOfMemoryException inträffade.
vid System.Windows.Forms.RichTextBox.StreamOut(Int32 flags)
vid System.Windows.Forms.RichTextBox.get_Text()
vid System.Windows.Forms.RichTextBox.GetCharIndexFromPosition(Point pt)
vid WhelkMud.WindowOutput.ExtendedRichTextBox.OnMouseMove(MouseEventArgs e) i D:\Repos\SharpKom\ExternalComponents\ExtendedRichTextBox.VisualDiff.cs:rad 48
vid System.Windows.Forms.Control.WmMouseMove(Message& m)
vid System.Windows.Forms.Control.WndProc(Message& m)
vid System.Windows.Forms.TextBoxBase.WndProc(Message& m)
vid System.Windows.Forms.RichTextBox.WndProc(Message& m)
vid System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
vid System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
vid System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Unhandled Exception
Kom version: 0.9.0.932
System.Environment.OSVersion = Microsoft Windows NT 6.0.6001 Service Pack 1
System.OutOfMemoryException: Ett undantagsfel av typen System.OutOfMemoryException inträffade.
vid System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
vid System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
vid SharpKom.GUI.SharpKomMessageDisplayStrategy.OnFoundValidDiffParentComplete(Text text) i D:\Repos\SharpKom\SharpKom\GUI\SharpKomMessageDisplayStrategy.cs:rad 155
vid SharpKom.Server.Server.<>c__DisplayClass15.<getcompletetextasync>b__13(Request[] r) i D:\Repos\SharpKom\SharpKom\Server\Server.cs:rad 377
vid SharpKom.RequestAggregator.RequestComplete(Request msg) i D:\Repos\SharpKom\SharpKom\Protocol Code\RequestAggregator.cs:rad 63
vid SharpKom.Request.OnComplete.Invoke(Request request)
vid SharpKom.Request.FireComplete() i D:\Repos\SharpKom\SharpKom\Protocol Code\Request.cs:rad 84
vid SharpKom.Request.OnPiggybackComplete(Request piggyRequest) i D:\Repos\SharpKom\SharpKom\Protocol Code\Request.cs:rad 110
vid SharpKom.Request.OnComplete.Invoke(Request request)
vid SharpKom.Request.FireComplete() i D:\Repos\SharpKom\SharpKom\Protocol Code\Request.cs:rad 84
vid SharpKom.Server.Connection.MessageReceivedComplete() i D:\Repos\SharpKom\SharpKom\Server\Connection.cs:rad 877
vid SharpKom.Server.Connection.OnDataReceived() i D:\Repos\SharpKom\SharpKom\Server\Connection.cs:rad 643
vid SharpKom.Server.Connection.OnReceiveComplete(IAsyncResult ar) i D:\Repos\SharpKom\SharpKom\Server\Connection.cs:rad 576
vid System.Net.LazyAsyncResult.Complete(IntPtr userToken)
vid System.Net.ContextAwareResult.CompleteCallback(Object state)
vid System.Threading.ExecutionContext.runTryCode(Object userData)
vid System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
vid System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
vid System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
vid System.Net.ContextAwareResult.Complete(IntPtr userToken)
vid System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
vid System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped nativeOverlapped)
vid System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped pOVERLAP)</getcompletetextasync>
Is there a specific text number that reproduces this problem?
Is the problem reproducible or was it one time only?
HTML and picture presented as plain text
It's reproducible
Correction:
It's reproducible meaning that it occurs whem I am looking back at the text. I have not tried to reproduce it with another text...
What is the text number?
Speedup the algorithm on large diffs and wrap everything in a try-catch.
I can not reproduce the exact error, it depends on the commented text also.
It is quite likely that the errors occurs due to some timeout-related issues.
The try-catch should catch remaining errors, but OutOfMemory errors have a tendency to propagate wildly to unrelated parts of the code.
I keep the bug open, please confirm if it is fixed or broken in the next release.
Fixed in version 1090.
It's still throwing an System.OutOfMemoryException. Do you want me to post a new crachdump? (version 0.10.0.1047)
No, please retest after 0.10.0.1090 or later is release (will probably be in a couple of days)
The application hangs in build 1098