Unexpected Error

[CharlesRHall]

I am just trying out the new version after bailing after having tried version 2.0 - and so far things have been flakey.

When I parse the first time, I get an Unexpected Error status in the toolbar, but no additional information that would help me track it down - the only option is to refresh.

And when I refresh I get the same status - first it says parsing error, then unexpected error

And when I click on Settings, it crashes Excel

[comintern]

Did it happen to create a log file?

[retailcoder]

The logs would confirm what specific "new version" you're using; you can find the logs under %appdata%\rubberduck\logs. They're disabled by default, but enabled on first startup specifically to log this kind of problem.

A parser error typically means your code doesn't compile. Does your VBA project compile? If you click the "parse error" button in the toolbar, a "parser errors" toolwindow should pop up with the actual parser error details - and these are in the logs too.

If your code does compile, then we would be very interested in getting to the bottom of this, since as far as we know at this point our parser handles every bit of legal VBA code we could possibly throw at it.

The crash on opening the settings window was a problem in an earlier build. Are you running 2.3.1?

[retailcoder]

Note that without further information about the version you're running and the parser error (i.e. the logs), there's nothing we can do other than shrug and say "it doesn't do that here".

[CharlesRHall]

RubberduckLog.txt

[CharlesRHall]

I disabled, /unloaded all my addins and com addins and the settings started to work
the log had been disabled, so I enabled it
my code compiles but I still get an error
see previous attachment

[bclothier]

@CharlesRHall is QS_TAI_SuplrRptApp.ReportTblCls your own code or some external library code?

[CharlesRHall]

my own code

[bclothier]

Ok, let's see if we can make a MCVE here. Can you create a new blank excel spreadsheet, and put only that procedure (and only what it actually needs -- mabye just the module?) and then try to parse that stripped down codebase?

[CharlesRHall]

does it parse all workbooks or just the active one - do I have to close the original before parsing?

[bclothier]

ATM, it will parse all unlocked VBA projects. To ensure no funny side effects, best to close all other workbooks and have only one workbook that contains the minimum code, ensure it is fully compiled then try to parse only that.

[retailcoder]

Rubberduck parses all (unlocked) projects loaded in the VBE, so yeah you'd have to close the original. Since this is an "out of memory" exception I'd actually recommend closing the process and launching a fresh one.

I'm rather curious about what other add-ins you're running - more specifically which one is interfering with our settings dialog...

The good news is that it's not quite a parser error, rather an exception that was thrown while acquiring the declarations in a specific module (which means that code was correctly parsed, so there's that!):

2018-12-13 14:18:08.6119;WARN-2.3.1.4308;Rubberduck.Common.LogLevelHelper;
Rubberduck version 2.3.1.4308 loading:
Operating System: Microsoft Windows NT 6.1.7601 Service Pack 1 x64
Host Product: Microsoft Office 2010 x86
Host Version: 14.0.7225.5000
Host Executable: EXCEL.EXE;
2018-12-13 14:18:23.8847;ERROR-2.3.1.4308;Rubberduck.Parsing.VBA.DeclarationResolving.DeclarationResolveRunnerBase;Exception thrown acquiring declarations for 'QS_TAI_SuplrRptApp.ReportTblCls' (thread 9).;System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.Collections.Concurrent.ConcurrentDictionary2..ctor(Int32 concurrencyLevel, Int32 capacity, Boolean growLockArray, IEqualityComparer1 comparer)
at System.Collections.Concurrent.ConcurrentDictionary2..ctor() at Rubberduck.Parsing.VBA.ModuleState..ctor(ConcurrentDictionary2 declarations) in C:\projects\rubberduck\Rubberduck.Parsing\VBA\ModuleState.cs:line 34
at Rubberduck.Parsing.VBA.RubberduckParserState.AddDeclaration(Declaration declaration) in C:\projects\rubberduck\Rubberduck.Parsing\VBA\RubberduckParserState.cs:line 756
at Rubberduck.Parsing.VBA.DeclarationResolving.DeclarationResolveRunnerBase.ResolveDeclarations(QualifiedModuleName module, IParseTree tree, IDictionary`2 projects, CancellationToken token) in C:\projects\rubberduck\Rubberduck.Parsing\VBA\DeclarationResolving\DeclarationResolveRunnerBase.cs:line 160

The exception being an OutOfMemoryException, I'm wondering a few things:

1. Does it also happen with that project on a 64-bit host?
2. How many other add-ins are loaded, and how much memory is the process consuming
3. How large is that particular module?
4. Are there a lot of type libraries are referenced by the VBA project?

[CharlesRHall]

ok - progress

once I unloaded my vbe addins then the parsing error went away

I use MZ-Tools 8.0 - VBA and VBE Tools 2.0