My Logos5 always crashes when I try to write my note in Chinese with my input method win32-chewing-0.4-dev.exe. I am glad to provide more info if you need.
-Kent
It sounds like you likely have something happening that the Logos techs will have to deal with; but I am fairly certain they will need logs to isolate the issue and identify a solution.
http://wiki.logos.com/Diagnostic_Logging
Thanks for your info.
Here is the text in my LogosCrash.txt. Please have a look.
Program Version: 5.0b SR-2 (5.0.2.0743)Windows Version: 6.1.7601.65536Time: 2013-04-11 08:53:13 +08:00 (2013-04-11T00:53:13Z)Installed memory: 1,912 MBInstall path: E:\...\Logos4\System\Logos.exeFree install space: 78,891 MBData path: E:\...\Logos4\Data\gmmmhhsp.pl0Free disk space: 78,891 MBTemp path: C:\Users\kent\AppData\Local\Temp\Free temp space: 24,225 MB
Error ID: 6363Error detail: IndexOutOfRangeException: Index was outside the bounds of the array.
System.IndexOutOfRangeException: Index was outside the bounds of the array. at System.Windows.Documents.ImmComposition.SetCompositionAdorner(Int32[] clauseInfo, Byte[] attributes) at System.Windows.Documents.ImmComposition.UpdateCompositionString(Char[] resultChars, Char[] compositionChars, Int32 caretOffset, Int32 deltaStart, Int32[] clauseInfo, Byte[] attributes) at System.Windows.Documents.ImmComposition.OnWmImeComposition(IntPtr hwnd, IntPtr lParam, Boolean& handled) at System.Windows.Documents.ImmComposition.ImmCompositionFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam) at MS.Win32.UnsafeNativeMethods.ITfMessagePump.GetMessageW(MSG& msg, IntPtr hwnd, Int32 msgFilterMin, Int32 msgFilterMax, Int32& result) at System.Windows.Threading.Dispatcher.GetMessage(MSG& msg, IntPtr hwnd, Int32 minMessage, Int32 maxMessage) at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame) at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame) at System.Windows.Threading.Dispatcher.Run() at System.Windows.Application.RunDispatcher(Object ignore) at System.Windows.Application.RunInternal(Window window) at System.Windows.Application.Run(Window window) at LDLS4.OurApp.InitializeAndRun(ReadOnlyCollection`1 listArgs, SingleInstanceManager sim) at LDLS4.OurApp.Main(String[] astrArgs)
You will need to contact Logos Support for this issue.
In the crash log you posted, all the functions on the call stack (i.e., the code that caused the crash) are part of WPF and authored by Microsoft (these are the "System.Windows" and "MS.Win32" lines). Unfortunately, this means that there is next to nothing we (Logos) can do to work around this crash; it appears to be a fundamental incompatibility between your IME and WPF (the Windows UI framework that we use). This is probably a bug you need to report to the IME vendor.
Thanks for your comment.
