Cymatic Trader for Betfair has stopped working

For software support - get help from Cymatic and the community

Cymatic Trader for Betfair has stopped working

Postby Angelo » Fri Nov 11, 2016 4:50 pm

Cymatic.jpg

Though not frequently, Advanced Cymatic Trader crashes occasionally on my Windows 10 [32-bit] machine.

Although I have faced no major impact due to this so far, it can potentially cause embarrassment sometimes.

The problem imo is mostly with the OS.

How can I know the exact reason for the same? Or how can I submit a crash report to Cymatic?

Thanks.
You do not have the required permissions to view the files attached to this post.
Angelo
 
Posts: 139
Joined: Mon Sep 28, 2015 5:41 am

Re: Cymatic Trader for Betfair has stopped working

Postby Gavin » Fri Nov 11, 2016 7:03 pm

Hi Angelo,

Thanks for contacting me and I'm sorry to hear about that. That problem has never been reported before, it looks like a generic Windows message and doesn't give any details about why the program crashed.

You could try looking at the event logs in Windows, by opening Event Viewer (type Event Viewer in Windows search / Cortana). Once in Event Viewer, try looking in both the Application Logs and System Logs and look for the details of the error.

Kind regards,

Gavin
User avatar
Gavin
Site Admin
 
Posts: 3835
Joined: Wed Jan 23, 2013 9:11 pm
Location: United Kingdom

Re: Cymatic Trader for Betfair has stopped working

Postby Angelo » Sat Nov 12, 2016 4:26 pm

The Event Viewer doesn't appear to show any details as per my current Windows settings, since a latest crash happened a few days ago. However, I will monitor it closely in the future in case of any such crashes, and will report here.

Thanks!
Angelo
 
Posts: 139
Joined: Mon Sep 28, 2015 5:41 am

Re: Cymatic Trader for Betfair has stopped working

Postby Gavin » Sun Nov 13, 2016 11:09 am

OK thanks Angelo.

Kind regards,

Gavin
User avatar
Gavin
Site Admin
 
Posts: 3835
Joined: Wed Jan 23, 2013 9:11 pm
Location: United Kingdom

Re: Cymatic Trader for Betfair has stopped working

Postby Angelo » Mon Nov 14, 2016 8:38 am

Well, in a rare incident, Cymatic has crashed today - sooner than expected.

I see 2 ERRORS in the Application Log of the Event Viewer. Here are the details:

=========================================================================================================

Log Name: Application
Source: Application Error
Date: 14/11/16 Mon 5:35:36 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-38TOM7K
Description:
Faulting application name: CyTraderBF.exe, version: 5.2.21.0, time stamp: 0x57d3fb8a
Faulting module name: comctl32.dll, version: 5.82.14393.447, time stamp: 0x5819c2cf
Exception code: 0xc0000005
Fault offset: 0x00043cce
Faulting process id: 0xfc4
Faulting application start time: 0x01d23e372b86c6e6
Faulting application path: C:\Users\ssssss\AppData\Local\Apps\2.0\AQAVXWY1.7T4\CYAHHYE5.MO7\cytr..tion_e95a99aca2c10e1b_0001.0000_b3347634ec7c3484\CyTraderBF.exe
Faulting module path: C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.14393.447_none_5507ded2cb4f7f4c\comctl32.dll
Report Id: dc70d078-0b9e-49d8-8465-0f4a3ac7795e
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-11-14T05:35:36.153914200Z" />
<EventRecordID>86498</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-38TOM7K</Computer>
<Security />
</System>
<EventData>
<Data>CyTraderBF.exe</Data>
<Data>5.2.21.0</Data>
<Data>57d3fb8a</Data>
<Data>comctl32.dll</Data>
<Data>5.82.14393.447</Data>
<Data>5819c2cf</Data>
<Data>c0000005</Data>
<Data>00043cce</Data>
<Data>fc4</Data>
<Data>01d23e372b86c6e6</Data>
<Data>C:\Users\ssssss\AppData\Local\Apps\2.0\AQAVXWY1.7T4\CYAHHYE5.MO7\cytr..tion_e95a99aca2c10e1b_0001.0000_b3347634ec7c3484\CyTraderBF.exe</Data>
<Data>C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.14393.447_none_5507ded2cb4f7f4c\comctl32.dll</Data>
<Data>dc70d078-0b9e-49d8-8465-0f4a3ac7795e</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

=======================


Log Name: Application
Source: .NET Runtime
Date: 14/11/16 Mon 5:35:35 AM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-38TOM7K
Description:
Application: CyTraderBF.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.NativeWindow.DefWndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.ToolTip.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.ToolTip+ToolTipNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application.Run(System.Windows.Forms.Form)
at  .()


Event Xml:
<Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='.NET Runtime'/><EventID Qualifiers='0'>1026</EventID><Level>2</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime='2016-11-14T05:35:35.982063100Z'/><EventRecordID>86497</EventRecordID><Channel>Application</Channel><Computer>DESKTOP-38TOM7K</Computer><Security/></System><EventData><Data>Application: CyTraderBF.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.NativeWindow.DefWndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.ToolTip.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.ToolTip+ToolTipNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application.Run(System.Windows.Forms.Form)
at  .()

</Data></EventData></Event>


=========================================================================================================

I have just checked for any Windows update, and found that my Windows 10 is up-to-date.

Thanks!
Angelo
 
Posts: 139
Joined: Mon Sep 28, 2015 5:41 am

Re: Cymatic Trader for Betfair has stopped working

Postby Gavin » Mon Nov 14, 2016 10:23 pm

Hi Angelo,

That is much appreciated, thanks for finding the error log.

This is caused by a bug in the Microsoft .NET Framework (which Cymatic uses to run). Specifically it is to do with the Tooltip on the data grids, these are the little messages that pop up on screen when you hover the mouse over certain cells in the data grids (for example the list of bets).

I detected an error that occurs if you use ALT + TAB to switch between applications when using Cymatic, if you do this just before the tooltip is shown. It is described here:

Access violation exception - on tooltip that faults comctl32.dll in .Net 4

From the information in that article it appears that I may be able to prevent the error if I disable tooltips, so I'll look into whether it is sensible to do that in Cymatic. However in the meantime, I think you should be able to avoid the error by avoiding using ALT + TAB to switch between applications, or if you do use ALT + TAB then avoid doing so when you have just started to hover the mouse over a data grid in Cymatic just before the tooltip appears.

Does that makes sense?

Kind regards,

Gavin
User avatar
Gavin
Site Admin
 
Posts: 3835
Joined: Wed Jan 23, 2013 9:11 pm
Location: United Kingdom

Re: Cymatic Trader for Betfair has stopped working

Postby Angelo » Tue Nov 15, 2016 3:25 am

Thanks for pinpointing the exact reason, Gavin.

I remember I was trying to use ALT+TAB at the time of the crash.

OK, I can avoid using it without any loss of functionality for my purpose.

Considering that my expertise in the particular topic is near-zero, a comment at the referenced page also says,

Code: Select all
The problem only occurs when visual styles are not enabled.

Adding Application.EnableVisualStyles() in main() before any forms are instantiated solves the problem.

which might be useful for consideration instead of disabling tooltips.

(By the way, I believe I have not used tooltips yet for my purpose)

Thanks!
Angelo
 
Posts: 139
Joined: Mon Sep 28, 2015 5:41 am

Re: Cymatic Trader for Betfair has stopped working

Postby Gavin » Tue Nov 15, 2016 9:50 am

Hi Angelo,

Thanks that is good to hear.

Yes, I read that part of the article afterwards and decided that it might be better to try to EnableVisualStyles rather than disabling tooltips (or to be precise, disabling them and then re-enabling them when focus changes back). Last night I enabled EnableVisualStyles in a test version. Actually, I had disabled visual styles some time ago in the past for another reason, because I noticed that when enabled it made the Betfair login button look a little bit different, so I'm checking fully again to see if that is something that still occurs or even matters. My plan is to test it on some different versions of Windows, so that hopefully I can just EnableVisualStyles and release a new version.

Thanks again and kind regards,

Gavin
User avatar
Gavin
Site Admin
 
Posts: 3835
Joined: Wed Jan 23, 2013 9:11 pm
Location: United Kingdom

Re: Cymatic Trader for Betfair has stopped working

Postby Angelo » Tue Nov 15, 2016 11:37 am

Thanks for your kind followup, Gavin. Much appreciated.
Angelo
 
Posts: 139
Joined: Mon Sep 28, 2015 5:41 am

Re: Cymatic Trader for Betfair has stopped working

Postby Angelo » Sat Dec 17, 2016 2:03 pm

Hello Gavin,

After a long time, I received the message 'Cymatic Trader for Betfair has stopped working', but this time, I don't remember using ALT+TAB . I have reproduced the message from the Event Viewer. Please advise. Thanks.

Code: Select all
Log Name: Application
Source: Application Error
Date: Sat 17 12 16 13:40:18
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-38TOM7K
Description:
Faulting application name: CyTraderBF.exe, version: 5.2.21.0, time stamp: 0x57d3fb8a
Faulting module name: comctl32.dll, version: 5.82.14393.447, time stamp: 0x5819c2cf
Exception code: 0xc0000005
Fault offset: 0x00043cce
Faulting process id: 0x1380
Faulting application start time: 0x01d25859abbb83ac
Faulting application path: C:\Users\xxxxx\AppData\Local\Apps\2.0\74VK8NRE.XGE\N181BL0D.KRJ\cytr..tion_e95a99aca2c10e1b_0001.0000_b3347634ec7c3484\CyTraderBF.exe
Faulting module path: C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.14393.447_none_5507ded2cb4f7f4c\comctl32.dll
Report Id: 6d2aacf0-d5e6-4942-a609-fc6d7a835f67
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
 <System>
 <Provider Name="Application Error" />
 <EventID Qualifiers="0">1000</EventID>
 <Level>2</Level>
 <Task>100</Task>
 <Keywords>0x80000000000000</Keywords>
 <TimeCreated SystemTime="2016-12-17T13:40:18.126718900Z" />
 <EventRecordID>120734</EventRecordID>
 <Channel>Application</Channel>
 <Computer>DESKTOP-38TOM7K</Computer>
 <Security />
 </System>
 <EventData>
 <Data>CyTraderBF.exe</Data>
 <Data>5.2.21.0</Data>
 <Data>57d3fb8a</Data>
 <Data>comctl32.dll</Data>
 <Data>5.82.14393.447</Data>
 <Data>5819c2cf</Data>
 <Data>c0000005</Data>
 <Data>00043cce</Data>
 <Data>1380</Data>
 <Data>01d25859abbb83ac</Data>
 <Data>C:\Users\xxxxx\AppData\Local\Apps\2.0\74VK8NRE.XGE\N181BL0D.KRJ\cytr..tion_e95a99aca2c10e1b_0001.0000_b3347634ec7c3484\CyTraderBF.exe</Data>
 <Data>C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.14393.447_none_5507ded2cb4f7f4c\comctl32.dll</Data>
 <Data>6d2aacf0-d5e6-4942-a609-fc6d7a835f67</Data>
 <Data>
 </Data>
 <Data>
 </Data>
 </EventData>
</Event>

----------------------------------


Log Name: Application
Source: .NET Runtime
Date: Sat 17 12 16 13:40:18
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-38TOM7K
Description:
Application: CyTraderBF.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhand exception.
Exception Info: System.AccessViolationException
 at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
 at System.Windows.Forms.NativeWindow.DefWndProc(System.Windows.Forms.Message ByRef)
 at System.Windows.Forms.ToolTip.WndProc(System.Windows.Forms.Message ByRef)
 at System.Windows.Forms.ToolTip+ToolTipNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
 at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
 at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
 at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
 at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
 at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
 at System.Windows.Forms.Application.Run(System.Windows.Forms.Form)
 at  .()


Event Xml:
<Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='.NET Runtime'/><EventID Qualifiers='0'>1026</EventID><Level>2</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime='2016-12-17T13:40:18.001842900Z'/><EventRecordID>120733</EventRecordID><Channel>Application</Channel><Computer>DESKTOP-38TOM7K</Computer><Security/></System><EventData><Data>Application: CyTraderBF.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhand exception.
Exception Info: System.AccessViolationException
 at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
 at System.Windows.Forms.NativeWindow.DefWndProc(System.Windows.Forms.Message ByRef)
 at System.Windows.Forms.ToolTip.WndProc(System.Windows.Forms.Message ByRef)
 at System.Windows.Forms.ToolTip+ToolTipNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
 at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
 at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
 at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
 at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
 at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
 at System.Windows.Forms.Application.Run(System.Windows.Forms.Form)
 at  .()

</Data></EventData></Event>

----------------------------------

Angelo
 
Posts: 139
Joined: Mon Sep 28, 2015 5:41 am

Next

Return to General Help / Support

Who is online

Users browsing this forum: No registered users and 0 guests