Rubberduck: Latest version 2.0.13.32288 crashes both Excel and Access 2016 when opening VBE

Created on 16 Mar 2017  Â·  24Comments  Â·  Source: rubberduck-vba/Rubberduck

Just installed this yesterday. When set to load on start-up it always crashes Access when I try to open the VBE (the crash is fatal, I don't get into the VBE and then Access closes).

Yesterday it was fine with Excel, but now I am getting the same issue there too. FYI the splash screen for Rubberduck opens, and then the crash happens.

When the crash happens I am given the option to close the prog or debug via Visual Studio (neither option keeps the program open).

No choice now but to uninstall as I cannot get into the VBE at all.

FYI I am using Win 10 640bit, but Office 2016 32-bit. Let me know if you need any more system/version info, or if there may be any log file of the error I can send to you

critical enhancement feature-settings

All 24 comments

FYI not sure if it is relevant but I have two other VBE add-ins loaded (which work fine, but perhaps may interfere?)

  • VBA Mz-Tools 3.0
  • EverytingAccess.com vbWatchdog

Hi and thanks for raising an issue.

Are you able confirm a few things?

  1. When you launch the VBE, are there any host-documents already open? Does it make a difference if there is a database file open when you launch VBE, or if Access doesn't have any databases open?

  2. If there is a database open, does it have any forms/reports showing, or any code running before you launch the VBE?

  3. With Rubberduck disabled, launch the VBE and close any open modules/userforms, then save. Re-enable Rubberduck and relaunch Access, load the same DB, and launch VBE. Does having all of the components in a closed state help with a stable launch?

  4. Are you able to disable the other add-ins, relaunch Access, and see if the problem persists?

Hi there.

Happy to (try!) and help. Would love to get it back working for me again!

So to answer:

When you launch the VBE, are there any host-documents already open? Does it make a difference if there is a database file open when you launch VBE, or if Access doesn't have any databases open?

I have only tried this with a database open. But I did try it with a very simple test DB with no VBA code and the problem persisted. Also, same problem in Excel when opened with a blank workbook. I will try both with no open file and get back to you.

If there is a database open, does it have any forms/reports showing, or any code running before you launch the VBE

No, same problem both in no-code DBs, and DB opened with shift to ensure nothing was running/open

With Rubberduck disabled, launch the VBE and close any open modules/userforms, then save. Re-enable Rubberduck and relaunch Access, load the same DB, and launch VBE. Does having all of the components in a closed state help with a stable launch?

Currently can’t disable RubberDuck, as I can’t get in to the VBE to do so! I will uninstall, reinstall and re-try. Or is there a way to disable RubberDuck from outside the VBE without uninstalling and reinstalling?

Are you able to disable the other add-ins, relaunch Access, and see if the problem persists?

Again, I’ll try this and see what happens.

I’ll give these tings a try and get back to you (likely it will be tomorrow now). Would you prefer a response on this email, or via my issue post on GitHub?

Duncan

@Jaspos Rubberduck's VBE add-in registry key has a value for LoadBehavior that the installer sets to 3 to load at startup - you can disable it without completely removing it by setting that value to 0:

regedit

Great, will try all this and let you know.

Duncan

I just noticed you have vbWatchdog installed... I need to check if the fix went into 2.0.13, but there is/was a parser issue with vbw-generated code.

Ok, I have been able to take a quick look now

  1. For both Excel and Access, when Rubberduck is set to load on start-up it crashes both XL & ACC when I launch the VBE, even with no workbook/DB open/no code running

  2. If not loaded at start-up, it still crashes both XL & ACC when in the VBE if I try to load RubberDuck

  3. If I disable vbWatchdog the problem persists

  4. If I disable both vbWatchdog and Mz-Tools (ie disable all other VBE add-ins I am running), the problem persists

So in summary, with no workbook or DBs open, no code running, and no other VBE add-ins loaded, Rubberduck still crashes ie I simply cannot get it to run on my machine.

FYI yesterday I did have it running for a while (it was fine in Excel, and if it didn’t load at start-up I could get into the VBE and then load it in Access and sometimes it would run fine).

But today, nada.

Sorry, this is probably not much help! But for now, for me, it is 100% a no-go.

Duncan

Duncan Salmon
www.alpine365.co.ukhttp://www.alpine365.co.uk/ | facebookhttps://www.facebook.com/pages/Alpine365/150986028258532?ref=hl | twitterhttps://twitter.com/alpine365ski

Is this logging anything to the RD log file? Also when you say...

the splash screen for Rubberduck opens, and then the crash happens

... do you mean that the splash screen is the only thing you see, or does it ever get as far as displaying the VBE window?

Finally - most of the time when you get debug prompt, that means the host process survived long enough to write an event to the Windows application log. Can you check to see if there are any details there? It would be in the Computer Management console under System Tools->Event Viewer->Windows Logs->Application.

OK….

  1. I only see the Rubbeduck splash screen, never get to see the VBE window. FYI I have attached a screenshot of the crash message in case it is of any use:

[cid:[email protected]]

  1. There ARE some Rubberduck logs, but they don’t appear related to the crashes, and only log my system info:

2017-03-15 19:17:25.0799;INFO-2.0.13.32288;Rubberduck.App;Rubberduck version 2.0.13.32288 loading:
Operating System: Microsoft Windows NT 10.0.14393.0 x64
Host Product: Microsoft Office 2016 x86
Host Version: 16.0.7369.2118
Host Executable: MSACCESS.EXE;

2017-03-16 10:28:08.0341;INFO-2.0.13.32288;Rubberduck.App;Rubberduck version 2.0.13.32288 loading:
Operating System: Microsoft Windows NT 10.0.14393.0 x64
Host Product: Microsoft Office 2016 x86
Host Version: 16.0.7369.2118
Host Executable: EXCEL.EXE;

FYI I have done a full search on my c drive for any files containing “rubberduck” and these are the only text files that show up

  1. Yes, I do have a windows fault log, I have attached the latest one here.

Hope some of this may help!

Duncan

Version=1
EventType=APPCRASH
EventTime=131341446932383111
ReportType=2
Consent=1
UploadTime=131341446933218911
ReportIdentifier=de36c2c0-0a4c-11e7-8367-6470026d274e
IntegratorReportIdentifier=de36c2bf-0a4c-11e7-8367-6470026d274e
WOW64=1
AppSessionGuid=00002768-0001-007a-184a-ec9c599ed201
TargetAppId=W:00061af7e574709cd9b1302d754d8cd7d2be00000000!00009970c40b0ebdb03b6d2ca6df2c70a0a31c5e9b5d!EXCEL.EXE
TargetAppVer=2017//02//20:02:43:43!20870fc!EXCEL.EXE
BootId=4294967295
Response.BucketId=e2d87b373fa6171b808e4e6a32c8fa0f
Response.BucketTable=1
Response.LegacyBucketId=108793748957
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=EXCEL.EXE
Sig[1].Name=Application Version
Sig[1].Value=16.0.7369.2118
Sig[2].Name=Application Timestamp
Sig[2].Value=58aa57df
Sig[3].Name=Fault Module Name
Sig[3].Value=KERNELBASE.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.14393.953
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=58ba586d
Sig[6].Name=Exception Code
Sig[6].Value=e0434352
Sig[7].Name=Exception Offset
Sig[7].Value=000da882
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.14393.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
UI[2]=C:Program Files (x86)Microsoft OfficerootOffice16EXCEL.EXE
UI[3]=Microsoft Excel has stopped working
UI[4]=Windows can check online for a solution to the problem and try to recover your information.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:Program Files (x86)Microsoft OfficerootOffice16EXCEL.EXE
LoadedModule[1]=C:WINDOWSSYSTEM32ntdll.dll
LoadedModule[2]=C:WINDOWSSystem32KERNEL32.DLL
LoadedModule[3]=C:WINDOWSSystem32KERNELBASE.dll
LoadedModule[4]=C:WINDOWSsystem32apphelp.dll
LoadedModule[5]=C:WINDOWSSystem32ucrtbase.dll
LoadedModule[6]=C:WINDOWSSystem32ADVAPI32.dll
LoadedModule[7]=C:WINDOWSSystem32msvcrt.dll
LoadedModule[8]=C:WINDOWSSYSTEM32VCRUNTIME140.dll
LoadedModule[9]=C:Program Files (x86)Microsoft OfficerootOffice16AppVIsvSubsystems32.dll
LoadedModule[10]=C:WINDOWSSYSTEM32MSVCP140.dll
LoadedModule[11]=C:WINDOWSSystem32sechost.dll
LoadedModule[12]=C:WINDOWSSystem32RPCRT4.dll
LoadedModule[13]=C:WINDOWSSystem32SspiCli.dll
LoadedModule[14]=C:WINDOWSSystem32CRYPTBASE.DLL
LoadedModule[15]=C:WINDOWSSystem32bcryptPrimitives.dll
LoadedModule[16]=C:WINDOWSSystem32ole32.dll
LoadedModule[17]=C:WINDOWSSystem32combase.dll
LoadedModule[18]=C:WINDOWSSystem32GDI32.dll
LoadedModule[19]=C:WINDOWSSystem32gdi32full.dll
LoadedModule[20]=C:WINDOWSSystem32USER32.dll
LoadedModule[21]=C:WINDOWSSystem32win32u.dll
LoadedModule[22]=C:Program Files (x86)Microsoft OfficerootOffice16oart.dll
LoadedModule[23]=C:WINDOWSSystem32SHELL32.dll
LoadedModule[24]=C:Program Files (x86)Microsoft OfficerootOffice16AppVIsvStream32.dll
LoadedModule[25]=C:WINDOWSSystem32cfgmgr32.dll
LoadedModule[26]=C:WINDOWSSystem32windows.storage.dll
LoadedModule[27]=C:WINDOWSSystem32powrprof.dll
LoadedModule[28]=C:WINDOWSSystem32shlwapi.dll
LoadedModule[29]=C:Program Files (x86)Microsoft OfficerootOffice16c2r32.dll
LoadedModule[30]=C:WINDOWSWinSxSx86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.14393.953_none_89c2555adb023171COMCTL32.dll
LoadedModule[31]=C:WINDOWSSystem32kernel.appcore.dll
LoadedModule[32]=C:WINDOWSSystem32shcore.dll
LoadedModule[33]=C:WINDOWSSystem32OLEAUT32.dll
LoadedModule[34]=C:WINDOWSWinSxSx86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.14393.953_none_baad48403594ab3fgdiplus.dll
LoadedModule[35]=C:WINDOWSSystem32msvcp_win.dll
LoadedModule[36]=C:WINDOWSSystem32profapi.dll
LoadedModule[37]=C:WINDOWSSYSTEM32USERENV.dll
LoadedModule[38]=C:WINDOWSSystem32IMM32.DLL
LoadedModule[39]=C:Program Files (x86)Common FilesMicrosoft SharedOffice16mso20win32client.dll
LoadedModule[40]=C:Program Files (x86)Common FilesMicrosoft SharedOffice16mso30win32client.dll
LoadedModule[41]=C:Program Files (x86)Common FilesMicrosoft SharedOffice16mso40uiwin32client.dll
LoadedModule[42]=C:Program Files (x86)Common FilesMicrosoft SharedOffice16mso98win32client.dll
LoadedModule[43]=C:WINDOWSSYSTEM32WTSAPI32.dll
LoadedModule[44]=C:Program Files (x86)Common FilesMicrosoft SharedOffice16mso99Lwin32client.dll
LoadedModule[45]=C:WINDOWSSYSTEM32MSIMG32.dll
LoadedModule[46]=C:Program Files (x86)Common FilesMicrosoft SharedOffice16mso.dll
LoadedModule[47]=C:WINDOWSSYSTEM32VERSION.dll
LoadedModule[48]=C:WINDOWSSYSTEM32msi.dll
LoadedModule[49]=C:WINDOWSSYSTEM32bcrypt.dll
LoadedModule[50]=C:WINDOWSSYSTEM32d2d1.dll
LoadedModule[51]=C:WINDOWSSystem32CRYPT32.dll
LoadedModule[52]=C:WINDOWSSystem32MSASN1.dll
LoadedModule[53]=C:WINDOWSsystem32uxtheme.dll
LoadedModule[54]=C:WINDOWSSystem32MSCTF.dll
LoadedModule[55]=C:Program Files (x86)RuiwareWinPatrolPATROLPRO.DLL
LoadedModule[56]=C:WINDOWSSYSTEM32WINSTA.dll
LoadedModule[57]=C:WINDOWSSYSTEM32dxgi.dll
LoadedModule[58]=C:WINDOWSsystem32dwmapi.dll
LoadedModule[59]=C:WINDOWSSYSTEM32d3d10_1.dll
LoadedModule[60]=C:WINDOWSSYSTEM32d3d10_1core.dll
LoadedModule[61]=C:WINDOWSSYSTEM32d3d11.dll
LoadedModule[62]=C:WINDOWSSYSTEM32D3D10Warp.dll
LoadedModule[63]=C:WINDOWSSystem32DriverStoreFileRepositorynv_dispi.inf_amd64_02838dee03d82b94nvwgf2um.dll
LoadedModule[64]=C:WINDOWSSYSTEM32WINMM.dll
LoadedModule[65]=C:WINDOWSSYSTEM32WINMMBASE.dll
LoadedModule[66]=C:WINDOWSsystem32nvspcap.dll
LoadedModule[67]=C:WINDOWSSystem32SETUPAPI.dll
LoadedModule[68]=C:WINDOWSSystem32PSAPI.DLL
LoadedModule[69]=C:WINDOWSSYSTEM32WINHTTP.dll
LoadedModule[70]=C:WINDOWSsystem32nvapi.dll
LoadedModule[71]=C:WINDOWSSYSTEM32Secur32.dll
LoadedModule[72]=C:WINDOWSSYSTEM32mscoree.dll
LoadedModule[73]=C:WindowsMicrosoft.NETFrameworkv4.0.30319mscoreei.dll
LoadedModule[74]=C:WINDOWSSYSTEM32DWrite.dll
LoadedModule[75]=C:Program Files (x86)Common FilesMicrosoft SharedOffice16riched20.dll
LoadedModule[76]=C:WINDOWSSYSTEM32DPAPI.dll
LoadedModule[77]=C:WINDOWSSystem32clbcatq.dll
LoadedModule[78]=C:WINDOWSSystem32netprofm.dll
LoadedModule[79]=C:WINDOWSSystem32WS2_32.dll
LoadedModule[80]=C:WINDOWSSystem32npmproxy.dll
LoadedModule[81]=C:WINDOWSSYSTEM32IPHLPAPI.DLL
LoadedModule[82]=C:WINDOWSSystem32NSI.dll
LoadedModule[83]=C:WINDOWSSYSTEM32XmlLite.dll
LoadedModule[84]=C:WINDOWSSYSTEM32sppc.dll
LoadedModule[85]=C:WINDOWSSYSTEM32webservices.dll
LoadedModule[86]=C:WINDOWSSystem32Normaliz.dll
LoadedModule[87]=C:WINDOWSSYSTEM32dhcpcsvc6.DLL
LoadedModule[88]=C:WINDOWSSYSTEM32dhcpcsvc.DLL
LoadedModule[89]=C:WINDOWSSYSTEM32ondemandconnroutehelper.dll
LoadedModule[90]=C:WINDOWSSYSTEM32urlmon.dll
LoadedModule[91]=C:WINDOWSSYSTEM32iertutil.dll
LoadedModule[92]=C:WINDOWSSYSTEM32WININET.dll
LoadedModule[93]=C:WINDOWSsystem32mswsock.dll
LoadedModule[94]=C:WINDOWSSYSTEM32DNSAPI.dll
LoadedModule[95]=C:WINDOWSSYSTEM32WINNSI.DLL
LoadedModule[96]=C:WINDOWSSYSTEM32webio.dll
LoadedModule[97]=C:WindowsSystem32rasadhlp.dll
LoadedModule[98]=C:Program Files (x86)Microsoft OfficerootOffice16gfx.dll
LoadedModule[99]=C:WindowsSystem32twinapi.appcore.dll
LoadedModule[100]=C:WINDOWSsystem32twinapi.dll
LoadedModule[101]=C:WindowsSystem32msxml6.dll
LoadedModule[102]=C:Program Files (x86)Microsoft OfficerootOffice16chart.dll
LoadedModule[103]=C:Program Files (x86)Microsoft OfficerootOffice16Ivy.dll
LoadedModule[104]=C:WINDOWSSystem32fwpuclnt.dll
LoadedModule[105]=C:WINDOWSSYSTEM32dcomp.dll
LoadedModule[106]=C:WINDOWSSystem32schannel.dll
LoadedModule[107]=C:WINDOWSsystem32propsys.dll
LoadedModule[108]=C:WINDOWSSYSTEM32MPR.DLL
LoadedModule[109]=C:WINDOWSSystem32coml2.dll
LoadedModule[110]=C:WINDOWSSYSTEM32mskeyprotect.dll
LoadedModule[111]=C:WINDOWSSYSTEM32ncrypt.dll
LoadedModule[112]=C:WINDOWSSYSTEM32NTASN1.dll
LoadedModule[113]=C:WINDOWSsystem32ncryptsslp.dll
LoadedModule[114]=C:Program Files (x86)Common FilesMicrosoft SharedVBAVBA7.1VBE7.DLL
LoadedModule[115]=C:WINDOWSSYSTEM32MSVCR100.dll
LoadedModule[116]=C:WINDOWSSYSTEM32CRYPTSP.dll
LoadedModule[117]=C:WINDOWSsystem32rsaenh.dll
LoadedModule[118]=C:WINDOWSSYSTEM32sxs.dll
LoadedModule[119]=C:WINDOWSsystem32dataexchange.dll
LoadedModule[120]=C:Program Files (x86)Common FilesMicrosoft SharedVBAVBA7.1VBEUI.DLL
LoadedModule[121]=C:WINDOWSSystem32WINTRUST.dll
LoadedModule[122]=C:Program Files (x86)Common FilesMicrosoft SharedVBAVBA7.11033VBE7INTL.DLL
LoadedModule[123]=C:WINDOWSsystem32directmanipulation.dll
LoadedModule[124]=C:WINDOWSSYSTEM32WindowsCodecs.dll
LoadedModule[125]=C:WINDOWSsystem32mlang.dll
LoadedModule[126]=C:WINDOWSSYSTEM32WINSPOOL.DRV
LoadedModule[127]=C:WindowsSystem32cryptnet.dll
LoadedModule[128]=C:WindowsSystem32thumbcache.dll
LoadedModule[129]=C:WINDOWSSYSTEM32policymanager.dll
LoadedModule[130]=C:WINDOWSSYSTEM32msvcp110_win.dll
LoadedModule[131]=C:WINDOWSSYSTEM32usp10.dll
LoadedModule[132]=C:WindowsSystem32Windows.Globalization.dll
LoadedModule[133]=C:WindowsSystem32Bcp47Langs.dll
LoadedModule[134]=C:WINDOWSSYSTEM32globinputhost.dll
LoadedModule[135]=C:Program Files (x86)Microsoft OfficeRootOffice16ADDINSPower View Excel Add-inAdHocReportingExcelClient.dll
LoadedModule[136]=C:WINDOWSSYSTEM32MSVCR120.dll
LoadedModule[137]=C:WINDOWSSYSTEM32MSVCP120.dll
LoadedModule[138]=C:Program Files (x86)Microsoft OfficeRootOffice16ADDINSPower Map Excel Add-inEXCELPLUGINSHELL.DLL
LoadedModule[139]=C:Program Files (x86)Microsoft OfficeRootOffice16ADDINSPowerPivot Excel Add-inPowerPivotExcelClientAddIn.dll
LoadedModule[140]=C:Program Files (x86)Microsoft OfficeRootOffice16ADDINSPowerPivot Excel Add-inResources1033PowerPivotExcelClientAddIn.rll
LoadedModule[141]=C:Program Files (x86)Microsoft OfficerootOffice16MSOHEV.DLL
LoadedModule[142]=c:Program Files (x86)Common FilesMicrosoft SharedVSTOvstoee.dll
LoadedModule[143]=c:Program Files (x86)Common FilesMicrosoft SharedVSTO10.0VSTOLoader.dll
LoadedModule[144]=C:WINDOWSSYSTEM32MSVCP100.dll
LoadedModule[145]=C:WINDOWSSYSTEM32oledlg.dll
LoadedModule[146]=c:Program Files (x86)Common FilesMicrosoft SharedVSTO10.01033VSTOLoaderUI.dll
LoadedModule[147]=C:Program Files (x86)Common FilesMicrosoft SharedSmart TagMOFL.DLL
LoadedModule[148]=C:WINDOWSSYSTEM32mfc140.dll
LoadedModule[149]=C:Program Files (x86)Common FilesMicrosoft SharedSmart Tag1033stintl.dll
LoadedModule[150]=C:WINDOWSWinSxSx86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.14393.447_none_5507ded2cb4f7f4cCOMCTL32.DLL
LoadedModule[151]=C:Program Files (x86)Common FilesMicrosoft SharedVBAVBA7.1VBEUIRES.DLL
LoadedModule[152]=C:Program Files (x86)Common FilesMicrosoft SharedVBAVBA7.11033VBEUIINTL.DLL
LoadedModule[153]=C:UsersDuncanAppDataRoamingEverythingAccess.comvbWatchdogvbWatchdog_AddIn.dll
LoadedModule[154]=C:WINDOWSSystem32COMDLG32.DLL
LoadedModule[155]=C:WINDOWSSystem32IMAGEHLP.DLL
LoadedModule[156]=C:WindowsMicrosoft.NETFrameworkv4.0.30319clr.dll
LoadedModule[157]=C:WINDOWSSYSTEM32MSVCR120_CLR0400.dll
LoadedModule[158]=C:WINDOWSassemblyNativeImages_v4.0.30319_32mscorlibf06d35cdb58e63c8a25f1658f23fd20dmscorlib.ni.dll
LoadedModule[159]=C:WindowsMicrosoft.NETFrameworkv4.0.30319clrjit.dll
LoadedModule[160]=C:WINDOWSassemblyNativeImages_v4.0.30319_32System6d712bf5f07ce74d9e2d31a443dea9c2System.ni.dll
LoadedModule[161]=C:WINDOWSassemblyNativeImages_v4.0.30319_32System.Core561bcb2835dc3d4de610397aebd07edcSystem.Core.ni.dll
LoadedModule[162]=C:WINDOWSassemblyNativeImages_v4.0.30319_32System.Configuration69bc7c6c084baf2d2ffd6871c726e266System.Configuration.ni.dll
LoadedModule[163]=C:WINDOWSassemblyNativeImages_v4.0.30319_32System.Xmlcfff018936a7c6348cb7ea98d432343aSystem.Xml.ni.dll
LoadedModule[164]=C:WINDOWSassemblyNativeImages_v4.0.30319_32System.ServiceModel4dc943422734eeb6a7a7ce0345166474System.ServiceModel.ni.dll
LoadedModule[165]=C:WINDOWSassemblyNativeImages_v4.0.30319_32System.Data79892cb4ea3329381a2fc51dad52eb6eSystem.Data.ni.dll
LoadedModule[166]=C:WINDOWSMicrosoft.NetassemblyGAC_32System.Datav4.0_4.0.0.0__b77a5c561934e089System.Data.dll
LoadedModule[167]=C:WINDOWSassemblyNativeImages_v4.0.30319_32System.Drawing058e016628ca385ecca0589255c71bceSystem.Drawing.ni.dll
LoadedModule[168]=C:WINDOWSassemblyNativeImages_v4.0.30319_32System.Runteb92aa12#d5101c374cd436c6638bd68d3e681438System.Runtime.Serialization.ni.dll
LoadedModule[169]=C:WINDOWSassemblyNativeImages_v4.0.30319_32stdolefa80c5dfd9f1c6661aee02e9e74ce6b5stdole.ni.dll
LoadedModule[170]=C:Program Files (x86)MZToolsMZTools3vba.dll
LoadedModule[171]=C:WINDOWSSYSTEM32MSVBVM60.DLL
LoadedModule[172]=C:Program Files (x86)Common FilesDesignerMSADDNDR.DLL
LoadedModule[173]=C:WINDOWSSystem32MSCOMCTL.OCX
LoadedModule[174]=C:WINDOWSassemblyNativeImages_v4.0.30319_32System.Windows.Forms68f0c8b24547a1eeafc998eb2b2522e0System.Windows.Forms.ni.dll
LoadedModule[175]=C:WINDOWSassemblyNativeImages_v4.0.30319_32WindowsBaseb87bf6675b253eeea9d7a1af759d1d9bWindowsBase.ni.dll
LoadedModule[176]=C:WINDOWSassemblyNativeImages_v4.0.30319_32System.Xml.Linq644006124f267e54cf6760ac688fbf3eSystem.Xml.Linq.ni.dll
LoadedModule[177]=C:WindowsMicrosoft.NETFrameworkv4.0.30319WPFPresentationNative_v0400.dll
LoadedModule[178]=C:WINDOWSassemblyNativeImages_v4.0.30319_32PresentationCore0e3670b79a0d3cf62dffca3403010d44PresentationCore.ni.dll
LoadedModule[179]=C:WINDOWSassemblyNativeImages_v4.0.30319_32Presentatio5ae0f00f#5fa817daff10898645f2a4f4514bee62PresentationFramework.ni.dll
LoadedModule[180]=C:WINDOWSassemblyNativeImages_v4.0.30319_32System.Xaml1b30fcb579bbaad955474f384a20d978System.Xaml.ni.dll
LoadedModule[181]=C:WINDOWSassemblyNativeImages_v4.0.30319_32System.Net.Http3eb2ab6d74a9d40ac970fb755a29c55eSystem.Net.Http.ni.dll
LoadedModule[182]=C:WINDOWSassemblyNativeImages_v4.0.30319_32WindowsForm0b574481#64624bdb3fc559d6ee63ace777078c7bWindowsFormsIntegration.ni.dll
LoadedModule[183]=C:WindowsMicrosoft.NETFrameworkv4.0.30319WPFwpfgfx_v0400.dll
LoadedModule[184]=C:WINDOWSSYSTEM32d3d9.dll
LoadedModule[185]=C:WINDOWSSystem32DriverStoreFileRepositorynv_dispi.inf_amd64_02838dee03d82b94nvd3dum.dll
LoadedModule[186]=C:WINDOWSassemblyNativeImages_v4.0.30319_32Presentatioaec034ca#3c7b6f1459cd44f3f3f9b59e5121a867PresentationFramework.Aero2.ni.dll
LoadedModule[187]=C:WINDOWSassemblyNativeImages_v4.0.30319_32Accessibilityf35dfe3d8f3dadab05287a86c8aa9b52Accessibility.ni.dll
LoadedModule[188]=C:WINDOWSassemblyNativeImages_v4.0.30319_32Presentatio1c9175f8#9ed2cf1e5bd07a30f5ccca893c0c99b7PresentationFramework.Aero.ni.dll
LoadedModule[189]=C:Program Files (x86)NVIDIA Corporation3D VisionnvSCPAPI.dll
LoadedModule[190]=C:WINDOWSassemblyNativeImages_v4.0.30319_32UIAutomationTypesb02077014cbc9078ead7391e8ee5fbe6UIAutomationTypes.ni.dll
LoadedModule[191]=C:WINDOWSSYSTEM32UIAutomationCore.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft Excel
AppPath=C:Program Files (x86)Microsoft OfficerootOffice16EXCEL.EXE
ApplicationIdentity=00000000000000000000000000000000
MetadataHash=-80953406

Rubberduck must be logging something, however IIRC I believe logging is disabled by default (or did we change that? can't remember...) - anyway if you go to %appdata%\Rubberduck, there should be a rubberduck.config xml file in there.. if you could crash RD just once more for us, I think we can get something to chew on.

Open up the configuration file in Notepad (or Notepad++), and find the <GeneralSettings> section near the top:

xml <GeneralSettings> <Language Code="en-US" /> <ShowSplash>true</ShowSplash> <SmartIndenterPrompted>false</SmartIndenterPrompted> <AutoSaveEnabled>false</AutoSaveEnabled> <AutoSavePeriod>10</AutoSavePeriod> <MinimumLogLevel>0</MinimumLogLevel> </GeneralSettings>

Set the MinimumLogLevel to 0, save & close the file, then bring up the VBE with Rubberduck enabled - when it crashes, I expect to see a detailed exception & stack trace in the logs: if you can share the contents of that log file here, I'm sure we can find out exactly what's happening.

Thanks!

Oh crap, sorry I missed the comment about there having RD logs - ignore my last comment. :neutral_face:

I wonder if maybe the settings file is corrupt, and RD is choking on the file.

You could try deleting the settings file, and RD should recreate it.

The settings file is located at %APPDATA%\Rubberduck\rubberduck.config

OK, that worked. A bit. Here’s what happened:

Worked a few times – but each time I closed the main app I got an message as if the app had crashed (“Excel is trying to recover your data, yada yada yada”), and then it reopened the file. Same for Access & XL

But now it’s back as it was ie crashed before getting to the VBE.

So this may well be related to the config file as I have re-deleted and it does the same as above,

NB I did make a change to “which windows open when RD opens” and then I couldn’t get to the VBE again - so I assume this will have altered the config file, so this could be the problem?

Duncan

Duncan Salmon
www.alpine365.co.ukhttp://www.alpine365.co.uk/ | facebookhttps://www.facebook.com/pages/Alpine365/150986028258532?ref=hl | twitterhttps://twitter.com/alpine365ski

[cid:[email protected]]

* Voted "One of the Best Alpine Chalets" by the Daily Telegraph *
T: +33 (0)9 81 93 71 10 | M: +33 (0)6 66 03 53 14
Alpine365 SARL | 2 La Régence | 69 route d’Hauteville | 73700 Bourg St Maurice | France
No SIRET: 509 636 007 00015 | No TVA: FR47 509 636 007

From: ThunderFrame [mailto:[email protected]]
Sent: 16 March 2017 20:02
To: rubberduck-vba/Rubberduck Rubberduck@noreply.github.com
Cc: Duncan Salmon A365 duncan@alpine365.co.uk; Mention mention@noreply.github.com
Subject: Re: [rubberduck-vba/Rubberduck] Latest version 2.0.13.32288 crashes both Excel and Access 2016 when opening VBE (#2878)

I wonder if maybe the settings file is corrupt, and RD is choking on the file.

You could try deleting the settings file, and RD should recreate it.

The settings file is located at %APPDATA%Rubberduckrubberduck.config

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/rubberduck-vba/Rubberduck/issues/2878#issuecomment-287159081, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ASc0Mi12pIaD6WwnIz9PXojfSux2y_wOks5rmYcfgaJpZM4MfCxe.

NB I did make a change to “which windows open when RD opens” and then I couldn’t get to the VBE again - so I assume this will have altered the config file, so this could be the problem?

I'm about 90% sure that is related to the issue. I'll see if I can replicate this with any settings combinations on my machine and do a bit of static analysis to try and identify bad code paths.

Cool.

If it helps the three windows I had selected were explorer, todo, and code analysis (? - can’t remember the exact name – the style cop one).

Don’t think I changed anything else.

I am based in Europe so likely will be off this now until tomorrow our time, will get back on to this as needed then.

Duncan

Duncan Salmon
www.alpine365.co.ukhttp://www.alpine365.co.uk/ | facebookhttps://www.facebook.com/pages/Alpine365/150986028258532?ref=hl | twitterhttps://twitter.com/alpine365ski

[cid:[email protected]]

* Voted "One of the Best Alpine Chalets" by the Daily Telegraph *
T: +33 (0)9 81 93 71 10 | M: +33 (0)6 66 03 53 14
Alpine365 SARL | 2 La Régence | 69 route d’Hauteville | 73700 Bourg St Maurice | France
No SIRET: 509 636 007 00015 | No TVA: FR47 509 636 007

From: comintern [mailto:[email protected]]
Sent: 16 March 2017 20:51
To: rubberduck-vba/Rubberduck Rubberduck@noreply.github.com
Cc: Duncan Salmon A365 duncan@alpine365.co.uk; Mention mention@noreply.github.com
Subject: Re: [rubberduck-vba/Rubberduck] Latest version 2.0.13.32288 crashes both Excel and Access 2016 when opening VBE (#2878)

NB I did make a change to “which windows open when RD opens” and then I couldn’t get to the VBE again - so I assume this will have altered the config file, so this could be the problem?

I'm about 90% sure that is related to the issue. I'll see if I can replicate this with any settings combinations on my machine and do a bit of static analysis to try and identify bad code paths.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/rubberduck-vba/Rubberduck/issues/2878#issuecomment-287171685, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ASc0MiSBWU-sSGv9CyAqzeGk7HyhsDirks5rmZKcgaJpZM4MfCxe.

We need to catch and log exceptions thrown on loading configuration...

I got a repro. My bad config file vs a new config file has more than just the window visibility differences, so I need to isolate the problem entries. There seems to be a mismatch in one of the inspection names for MalformedAnnotation/AnnotationMissingArgument, but I'm on my work PC now... Once I get back to my laptop, I'll dig into this more.

This made me think – would it be useful if I sent you a copy of my (presumably corrupt) config file after I have this problem?

From: ThunderFrame [mailto:[email protected]]
Sent: 29 March 2017 00:09
To: rubberduck-vba/Rubberduck Rubberduck@noreply.github.com
Cc: Duncan Salmon A365 duncan@alpine365.co.uk; Mention mention@noreply.github.com
Subject: Re: [rubberduck-vba/Rubberduck] Latest version 2.0.13.32288 crashes both Excel and Access 2016 when opening VBE (#2878)

I got a repro. My bad config file vs a new config file has more than just the window visibility differences, so I need to isolate the problem entries. There seems to be a mismatch in one of the inspection names for MalformedAnnotation/AnnotationMissingArgument, but I'm on my work PC now... Once I get back to my laptop, I'll dig into this more.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/rubberduck-vba/Rubberduck/issues/2878#issuecomment-289920266, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ASc0Mq-mIdOyMfCUCi6AUyJW-O5wUuFjks5rqYUMgaJpZM4MfCxe.

@Jaspos It might be useful to see your config file, but I've just done some testing, and while toggling the visibility of Windows did recreate this crash, the crash seems to be related to the window hooks and not the config settings themselves.

While I was able to recreate the crash on startup by setting the visibility of Code Explorer and Code Inspections to true, I found that the crash only occurred when I had those windows arranged in the same docking "Frame" as the Properties window. When Rubberduck starts, it temporarily displays all of the ToolWindows, ensures they're sized appropriately (using EnsureMinimumWindowSize), and then closes them unless the startup visibility is set to True, in which case it is left visible.

I can have the window visibility set to true in the Rubberduck config, without the host crashing, but only if I have the ToolWindows docked in a different docking frame to the Properties window.

The screencap below shows Rubberduck crashing after a manual toolwindow movement (with the Properties window being in the same dock). I suspect this is the same crash that is being triggered by the display of ToolWindows in the startup process.

toolwindowplacement

Same issue here and also most probably related to the rearranged windows. I removed the config file and Rubberduck started again. Here's the config file before I removed it:

<?xml version="1.0" encoding="utf-8"?>
<Configuration>
  <GeneralSettings>
    <Language Code="de-DE" />
    <ShowSplash>true</ShowSplash>
    <CheckVersion>true</CheckVersion>
    <SmartIndenterPrompted>false</SmartIndenterPrompted>
    <AutoSaveEnabled>false</AutoSaveEnabled>
    <AutoSavePeriod>10</AutoSavePeriod>
    <MinimumLogLevel>6</MinimumLogLevel>
  </GeneralSettings>
  <HotkeySettings>
    <Settings>
      <HotkeySetting>
        <Name>IndentProcedure</Name>
        <Key1>P</Key1>
        <IsEnabled>true</IsEnabled>
        <HasShiftModifier>false</HasShiftModifier>
        <HasAltModifier>false</HasAltModifier>
        <HasCtrlModifier>true</HasCtrlModifier>
      </HotkeySetting>
      <HotkeySetting>
        <Name>IndentModule</Name>
        <Key1>M</Key1>
        <IsEnabled>true</IsEnabled>
        <HasShiftModifier>false</HasShiftModifier>
        <HasAltModifier>false</HasAltModifier>
        <HasCtrlModifier>true</HasCtrlModifier>
      </HotkeySetting>
      <HotkeySetting>
        <Name>CodeExplorer</Name>
        <Key1>R</Key1>
        <IsEnabled>true</IsEnabled>
        <HasShiftModifier>false</HasShiftModifier>
        <HasAltModifier>false</HasAltModifier>
        <HasCtrlModifier>true</HasCtrlModifier>
      </HotkeySetting>
      <HotkeySetting>
        <Name>FindSymbol</Name>
        <Key1>T</Key1>
        <IsEnabled>true</IsEnabled>
        <HasShiftModifier>false</HasShiftModifier>
        <HasAltModifier>false</HasAltModifier>
        <HasCtrlModifier>true</HasCtrlModifier>
      </HotkeySetting>
      <HotkeySetting>
        <Name>InspectionResults</Name>
        <Key1>I</Key1>
        <IsEnabled>true</IsEnabled>
        <HasShiftModifier>true</HasShiftModifier>
        <HasAltModifier>false</HasAltModifier>
        <HasCtrlModifier>true</HasCtrlModifier>
      </HotkeySetting>
      <HotkeySetting>
        <Name>TestExplorer</Name>
        <Key1>T</Key1>
        <IsEnabled>true</IsEnabled>
        <HasShiftModifier>true</HasShiftModifier>
        <HasAltModifier>false</HasAltModifier>
        <HasCtrlModifier>true</HasCtrlModifier>
      </HotkeySetting>
      <HotkeySetting>
        <Name>RefactorMoveCloserToUsage</Name>
        <Key1>C</Key1>
        <IsEnabled>true</IsEnabled>
        <HasShiftModifier>true</HasShiftModifier>
        <HasAltModifier>false</HasAltModifier>
        <HasCtrlModifier>true</HasCtrlModifier>
      </HotkeySetting>
      <HotkeySetting>
        <Name>RefactorRename</Name>
        <Key1>R</Key1>
        <IsEnabled>true</IsEnabled>
        <HasShiftModifier>true</HasShiftModifier>
        <HasAltModifier>false</HasAltModifier>
        <HasCtrlModifier>true</HasCtrlModifier>
      </HotkeySetting>
      <HotkeySetting>
        <Name>RefactorExtractMethod</Name>
        <Key1>M</Key1>
        <IsEnabled>true</IsEnabled>
        <HasShiftModifier>true</HasShiftModifier>
        <HasAltModifier>false</HasAltModifier>
        <HasCtrlModifier>true</HasCtrlModifier>
      </HotkeySetting>
      <HotkeySetting>
        <Name>SourceControl</Name>
        <Key1>D6</Key1>
        <IsEnabled>true</IsEnabled>
        <HasShiftModifier>true</HasShiftModifier>
        <HasAltModifier>false</HasAltModifier>
        <HasCtrlModifier>true</HasCtrlModifier>
      </HotkeySetting>
      <HotkeySetting>
        <Name>RefactorEncapsulateField</Name>
        <Key1>E</Key1>
        <IsEnabled>true</IsEnabled>
        <HasShiftModifier>true</HasShiftModifier>
        <HasAltModifier>false</HasAltModifier>
        <HasCtrlModifier>true</HasCtrlModifier>
      </HotkeySetting>
      <HotkeySetting>
        <Name>ParseAll</Name>
        <Key1></Key1>
        <IsEnabled>true</IsEnabled>
        <HasShiftModifier>false</HasShiftModifier>
        <HasAltModifier>false</HasAltModifier>
        <HasCtrlModifier>true</HasCtrlModifier>
      </HotkeySetting>
    </Settings>
  </HotkeySettings>
  <ToDoListSettings>
    <ToDoMarkers>
      <ToDoMarker Text="NOTE " />
      <ToDoMarker Text="TODO " />
      <ToDoMarker Text="BUG " />
    </ToDoMarkers>
  </ToDoListSettings>
  <CodeInspectionSettings>
    <CodeInspections>
      <CodeInspection Name="ObjectVariableNotSetInspection" Severity="Suggestion" InspectionType="CodeQualityIssues" />
      <CodeInspection Name="FunctionReturnValueNotUsedInspection" Severity="Warning" InspectionType="CodeQualityIssues" />
      <CodeInspection Name="SelfAssignedDeclarationInspection" Severity="Hint" InspectionType="CodeQualityIssues" />
      <CodeInspection Name="MoveFieldCloserToUsageInspection" Severity="Suggestion" InspectionType="CodeQualityIssues" />
      <CodeInspection Name="EncapsulatePublicFieldInspection" Severity="Suggestion" InspectionType="MaintainabilityAndReadabilityIssues" />
      <CodeInspection Name="EmptyStringLiteralInspection" Severity="Warning" InspectionType="LanguageOpportunities" />
      <CodeInspection Name="ImplicitActiveSheetReferenceInspection" Severity="Warning" InspectionType="MaintainabilityAndReadabilityIssues" />
      <CodeInspection Name="ImplicitActiveWorkbookReferenceInspection" Severity="Warning" InspectionType="MaintainabilityAndReadabilityIssues" />
      <CodeInspection Name="MultipleFolderAnnotationsInspection" Severity="Error" InspectionType="MaintainabilityAndReadabilityIssues" />
      <CodeInspection Name="ProcedureCanBeWrittenAsFunctionInspection" Severity="Suggestion" InspectionType="LanguageOpportunities" />
      <CodeInspection Name="UseMeaningfulNameInspection" Severity="Suggestion" InspectionType="MaintainabilityAndReadabilityIssues" />
      <CodeInspection Name="WriteOnlyPropertyInspection" Severity="Suggestion" InspectionType="CodeQualityIssues" />
      <CodeInspection Name="UntypedFunctionUsageInspection" Severity="Hint" InspectionType="LanguageOpportunities" />
      <CodeInspection Name="AssignedByValParameterInspection" Severity="Warning" InspectionType="LanguageOpportunities" />
      <CodeInspection Name="ConstantNotUsedInspection" Severity="Warning" InspectionType="CodeQualityIssues" />
      <CodeInspection Name="DefaultProjectNameInspection" Severity="Suggestion" InspectionType="MaintainabilityAndReadabilityIssues" />
      <CodeInspection Name="ImplicitPublicMemberInspection" Severity="Hint" InspectionType="MaintainabilityAndReadabilityIssues" />
      <CodeInspection Name="MultilineParameterInspection" Severity="Suggestion" InspectionType="MaintainabilityAndReadabilityIssues" />
      <CodeInspection Name="NonReturningFunctionInspection" Severity="Error" InspectionType="CodeQualityIssues" />
      <CodeInspection Name="ObsoleteCallStatementInspection" Severity="Suggestion" InspectionType="LanguageOpportunities" />
      <CodeInspection Name="ObsoleteGlobalInspection" Severity="Suggestion" InspectionType="LanguageOpportunities" />
      <CodeInspection Name="ObsoleteLetStatementInspection" Severity="Suggestion" InspectionType="LanguageOpportunities" />
      <CodeInspection Name="ObsoleteTypeHintInspection" Severity="Suggestion" InspectionType="LanguageOpportunities" />
      <CodeInspection Name="OptionBaseInspection" Severity="Hint" InspectionType="MaintainabilityAndReadabilityIssues" />
      <CodeInspection Name="ParameterCanBeByValInspection" Severity="Suggestion" InspectionType="CodeQualityIssues" />
      <CodeInspection Name="ParameterNotUsedInspection" Severity="Warning" InspectionType="CodeQualityIssues" />
      <CodeInspection Name="ProcedureNotUsedInspection" Severity="Warning" InspectionType="CodeQualityIssues" />
      <CodeInspection Name="UnassignedVariableUsageInspection" Severity="Error" InspectionType="CodeQualityIssues" />
      <CodeInspection Name="VariableNotUsedInspection" Severity="Warning" InspectionType="CodeQualityIssues" />
      <CodeInspection Name="VariableNotAssignedInspection" Severity="Warning" InspectionType="CodeQualityIssues" />
      <CodeInspection Name="ImplicitByRefParameterInspection" Severity="Hint" InspectionType="CodeQualityIssues" />
      <CodeInspection Name="ImplicitVariantReturnTypeInspection" Severity="Hint" InspectionType="CodeQualityIssues" />
      <CodeInspection Name="MultipleDeclarationsInspection" Severity="Warning" InspectionType="MaintainabilityAndReadabilityIssues" />
      <CodeInspection Name="ObsoleteCommentSyntaxInspection" Severity="Suggestion" InspectionType="LanguageOpportunities" />
      <CodeInspection Name="OptionExplicitInspection" Severity="Error" InspectionType="CodeQualityIssues" />
      <CodeInspection Name="VariableTypeNotDeclaredInspection" Severity="Warning" InspectionType="LanguageOpportunities" />
      <CodeInspection Name="MissingAnnotationArgumentInspection" Severity="Error" InspectionType="CodeQualityIssues" />
    </CodeInspections>
    <WhitelistedIdentifiers />
    <RunInspectionsOnSuccessfulParse>true</RunInspectionsOnSuccessfulParse>
  </CodeInspectionSettings>
  <UnitTestSettings>
    <BindingMode>LateBinding</BindingMode>
    <AssertMode>StrictAssert</AssertMode>
    <ModuleInit>true</ModuleInit>
    <MethodInit>true</MethodInit>
    <DefaultTestStubInNewModule>false</DefaultTestStubInNewModule>
  </UnitTestSettings>
  <IndenterSettings>
    <IndentEntireProcedureBody>true</IndentEntireProcedureBody>
    <IndentFirstCommentBlock>true</IndentFirstCommentBlock>
    <IndentEnumTypeAsProcedure>false</IndentEnumTypeAsProcedure>
    <IndentFirstDeclarationBlock>true</IndentFirstDeclarationBlock>
    <AlignCommentsWithCode>true</AlignCommentsWithCode>
    <AlignContinuations>true</AlignContinuations>
    <IgnoreOperatorsInContinuations>true</IgnoreOperatorsInContinuations>
    <IndentCase>false</IndentCase>
    <ForceDebugStatementsInColumn1>false</ForceDebugStatementsInColumn1>
    <ForceCompilerDirectivesInColumn1>false</ForceCompilerDirectivesInColumn1>
    <IndentCompilerDirectives>true</IndentCompilerDirectives>
    <AlignDims>false</AlignDims>
    <AlignDimColumn>15</AlignDimColumn>
    <EndOfLineCommentStyle>AlignInColumn</EndOfLineCommentStyle>
    <EndOfLineCommentColumnSpaceAlignment>50</EndOfLineCommentColumnSpaceAlignment>
    <IndentSpaces>4</IndentSpaces>
    <VerticallySpaceProcedures>true</VerticallySpaceProcedures>
    <LinesBetweenProcedures>1</LinesBetweenProcedures>
  </IndenterSettings>
  <WindowSettings>
    <CodeExplorerVisibleOnStartup>true</CodeExplorerVisibleOnStartup>
    <CodeInspectionsVisibleOnStartup>false</CodeInspectionsVisibleOnStartup>
    <SourceControlVisibleOnStartup>false</SourceControlVisibleOnStartup>
    <TestExplorerVisibleOnStartup>true</TestExplorerVisibleOnStartup>
    <TodoExplorerVisibleOnStartup>true</TodoExplorerVisibleOnStartup>
  </WindowSettings>
</Configuration>

(I removed the Key for ParseAll as it contained a code quote character)

FYI I haven’t had a chance to look at this again yet, but I can confirm that I definitely had docked windows, including Code Explorer docked in the same frame as the Properties window.

Duncan

Duncan Salmon
www.alpine365.co.ukhttp://www.alpine365.co.uk/ | facebookhttps://www.facebook.com/pages/Alpine365/150986028258532?ref=hl | twitterhttps://twitter.com/alpine365ski

[cid:[email protected]]

* Voted "One of the Best Alpine Chalets" by the Daily Telegraph *
T: +33 (0)9 81 93 71 10 | M: +33 (0)6 66 03 53 14
Alpine365 SARL | 2 La Régence | 69 route d’Hauteville | 73700 Bourg St Maurice | France
No SIRET: 509 636 007 00015 | No TVA: FR47 509 636 007

From: JoergBr [mailto:[email protected]]
Sent: 02 April 2017 16:33
To: rubberduck-vba/Rubberduck Rubberduck@noreply.github.com
Cc: Duncan Salmon A365 duncan@alpine365.co.uk; Mention mention@noreply.github.com
Subject: Re: [rubberduck-vba/Rubberduck] Latest version 2.0.13.32288 crashes both Excel and Access 2016 when opening VBE (#2878)

Same issue here and also most probably related to the rearranged windows. I removed the config file and RubberDuck startet again. Here's the config file before I removed it:
true true false false 10 6 IndentProcedure P true false false true IndentModule M true false false true CodeExplorer R true false false true FindSymbol T true false false true InspectionResults I true true false true TestExplorer T true true false true RefactorMoveCloserToUsage C true true false true RefactorRename R true true false true RefactorExtractMethod M true true false true SourceControl D6 true true false true RefactorEncapsulateField E true true false true ParseAll ` true false false true true LateBinding StrictAssert true true false true true false true true true true false false false true false 15 AlignInColumn 50 4 true 1 true false false true true

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/rubberduck-vba/Rubberduck/issues/2878#issuecomment-290990074, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ASc0MpJG64l9d20F4qMYQLyxwNun6bMxks5rr7GggaJpZM4MfCxe.

Me too had docked windows on the left and on the bottom of the VBE window for RubberDuck.

I've been able to narrow things down a bit. After removing the config file and restarting RubberDuck, the crash reoccured when I tried to show the "ToDo Items" which I had docked to the Direct Window before. I removed the config file again, restarted RubberDuck and then opened the Options Menu of the VBE first. On the Docking tab, I disabled the docking of the Direct Window. After opening the "ToDo Items" then, RubberDuck did NOT crash. So it must be an issue related with the docking to the Direct Window which was at the window bottom.

VBE docking is outside our control. We do have some issues with docking, but there are plans to completely change how all of that is working, so I'm closing this issue for now.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Hosch250 picture Hosch250  Â·  3Comments

retailcoder picture retailcoder  Â·  4Comments

SteGriff picture SteGriff  Â·  3Comments

Gener4tor picture Gener4tor  Â·  3Comments

ChrisBrackett picture ChrisBrackett  Â·  3Comments