v7 Crash when closing SSMS

v7
SQL Management Studio 10.50.4270

Sometimes after some usage of SQL Assistant, when closing SSMS, I get a crash message.

If I simply open and close SSMS, no issue
A few basic queries, no issue
Significant usage for some time, issue.

Would you please check SQL Assistant's log file for any exceptions recorded there?
The file is located in %APPDATA%\SQL Assistant\7.0\SqlAssist.log

7/2/2014 2:19:51 PM ssms.exe Error: Exception: SubclassWndProc(675,0,0)
Access violation at address 0DB15C2B in module 'SqlAssistPrefs.dll'. Read of address 68706D20
operating system : Windows 7 x64 Service Pack 1 build 7601
system language : English
system up time : 4 days 19 hours
program up time : 1 minute 50 seconds
processors : 8x Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz
physical memory : 3437/8118 MB (free/total)
free disk space : (C:) 51.15 GB
display mode : 1920x1080, 32 bit
process id : $2e50
allocated memory : 147.89 MB
<SNIP>

executable : ssms.exe
current module : SqlAssistPrefs.dll
module date/time : 2014-06-30 16:15
version : 7.0.133.0
callstack crc : $5ff9e0d4, $638e9d2f, $919adfc8
exception number : 1
exception class : EAccessViolation
exception message : Access violation at address 0DB15C2B in module 'SqlAssistPrefs.dll'. Read of address 68706D20.

Main ($1f00):
0db15c2b +007 SqlAssistPrefs.dll System 667 +0 @LStrFromPChar
0dcbf3ae +182 SqlAssistPrefs.dll AssistPan 365 +35 FormatName
0dcbf5ed +029 SqlAssistPrefs.dll AssistPan 427 +1 GetText
0dcc2d7e +08a SqlAssistPrefs.dll AssistPan 1570 +9 TAPNode.GetTextData
0dcc2b73 +70f SqlAssistPrefs.dll AssistPan 1522 +120 TAPNode._Paint
0dca03e8 +12c SqlAssistPrefs.dll PanUnit 386 +28 TPanNode.Paint
0dca0bb6 +022 SqlAssistPrefs.dll PanUnit 733 +2 TPNGroup._Paint
0dca03e8 +12c SqlAssistPrefs.dll PanUnit 386 +28 TPanNode.Paint
0dca08bd +021 SqlAssistPrefs.dll PanUnit 549 +3 TPanNode.SetMouseOver
0dcc3d5b +00f SqlAssistPrefs.dll AssistPan 1901 +2 TAPRow.SetMouseOver
0dcc37d0 +010 SqlAssistPrefs.dll AssistPan 1771 +2 TAPNode.SetMouseOver
0dca19c6 +022 SqlAssistPrefs.dll PanUnit 1274 +6 TPan.SetNodeOver
0dca1872 +006 SqlAssistPrefs.dll PanUnit 1235 +1 TPan.MouseEnter
0dca15e1 +231 SqlAssistPrefs.dll PanUnit 1135 +56 TPan.WndProc
0dcca2f2 +016 SqlAssistPrefs.dll AssistPan 3659 +2 TAssistPan.WndProc
0dc9122c +060 SqlAssistPrefs.dll Subclass 71 +6 SubclassWndProc

thread $1838:
0de6a403 +1f SqlAssistPrefs.dll ArtIntelPan 770 +1 TBaseSearchThread.Execute

cpu registers:
eax = 003af098
ebx = 00000000
ecx = 00000000
edx = 68706d20
esi = 0df1fe91
edi = 68706d20
eip = 0db15c2b
esp = 003af078
ebp = 003af0bc

disassembling:
[...]
0db15c24 public System.@LStrFromPChar: ; function entry point
0db15c24 xor ecx, ecx
0db15c26 test edx, edx
0db15c28 jz loc_db15c4b
0db15c2a push edx
0db15c2b > cmp cl, [edx]
0db15c2d jz loc_db15c46
0db15c2f cmp cl, [edx+1]
0db15c32 jz loc_db15c45
0db15c34 cmp cl, [edx+2]
0db15c37 jz loc_db15c44
[...]

Thank you for your prompt response. I'm going to enter this info into our tracking system and ask development team to follow up.

Same thing happens to me, probably more than 50% of the time when closing SSMS. It happens with SQL Assistant v7 beta, but also happened with v6 since at least 2013, hard to remember exactly when. Happened for me with SSMS 2008 R2, 2012, 2014 (I have not tried others). I am using Windows 7 x64.

In my case the SqlAssist.log does not always indicate a problem, but Windows crash reporter always shows it as a buffer exception:

Code:

Problem signature:
Problem Event Name: BEX
Application Name: Ssms.exe
Application Version: 2014.120.2000.8
Application Timestamp: 5306c06d
Fault Module Name: SqlAssistPrefs.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 53b1c559
Exception Offset: 14eb71de
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: fa66
Additional Information 2: fa6696398de2b9f98383d7a3bf5c3ea1
Additional Information 3: fa66
Additional Information 4: fa6696398de2b9f98383d7a3bf5c3ea1

Thank you very much. This might help to pinpoint the root cause. I will pass it to the development team.