New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error Resolving #2845
Comments
Hi and thanks for raising an issue. I've only skimmed the logs, but it would be helpful if you could confirm that your VBA project compiles. Rubberduck relies on the VBA code being in a compilable state. You can check if your project compiles by choosing Debug..Compile in the VBE. The errors seem to be occurring with modules.
Are you perhaps able to share those modules? |
Hello ThunderFrame! Yes the project does compile without any errors. I can post the module mdlFehlerbehandlung as it is the smallest of those modules you mentioned:
|
Sometimes I love .NET and sometimes I hate it ... this time I'm not quite sure yet:
Seems we're trying to resolve a reference that doesn't exist yet and the Dictionary Lookup blows up here ... @MDoerner you did some major changes around there IIUC. Maybe you can shed some light? |
I cannot reproduce the issue with the current build and the module provided. @ChriHi Could you try whether the issue still exists with the freshly released hotfix release 2.0.13? |
Hello MDoerner! I installed the hotfix release - thanks for the quick support!
|
btw - I don't know whether this is relevant or not but I do not recognize the path "C:\Users\hosch..." mentioned in the logfile. There is no such User on my System. |
@ChriHi I suspect this would be an intermittent/unpredictable issue that doesn't reliably occur (COM interop is fun like that!) - does it happen again if you exit completely and restart Excel? |
Just to be sure I rebooted Windows. I still get the error but this time I first got a messagebox saying "not enough memory". As I mentioned before I am completely new to rubberduck. Are there maybe any settings I have to check or any (obvious) mistakes, maybe some libraries you are not supposed to use? |
@ChriHi we'd like Rubberduck to "just work" with everything people can throw at it - that OOM message is worrying me. Are you loading the VBE with an empty VBA project? If not, what libraries are you referencing? Is there anything in the logs about that error? |
heres the logfile from after the reboot:
I do open a .xlsm file with quite some code in it (like module I posted earlier). When opening VBE/rubberduck from a newly created/empty file everything works just fine. However even when quitting this empty file I also do get the crash on exit mentioned in the known issues. My project uses the following libraries:
|
Do you have any other VBE add-ins installed? |
no, this is the first add-in i've ever used. |
Can you repro with the latest 2.1 pre-release build? |
The issue mentions OOM, which can be left to the #3347 and because of its age, we'll close this. If anyone experiences, feel free to reopen. |
Hello,
I'm new to rubberduck (and Github for that matter) and wanted to run it for the first time.
However I always get the error "Error Resolving" when opening my Excel project. I enabled logging (trace) and rubberduck creates about 6MB of logfiles. I've attached both logfiles. Any help is very much welcome!
RubberduckLog.txt
RubberduckLog.1.txt
The text was updated successfully, but these errors were encountered: