Skip to content
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

Frequent Access 2021 crashes during code parsing #6144

Closed
rkorne opened this issue Aug 24, 2023 · 3 comments
Closed

Frequent Access 2021 crashes during code parsing #6144

rkorne opened this issue Aug 24, 2023 · 3 comments
Labels
bug Identifies work items for known bugs critical Marks a bug as a must-fix, showstopper issue duplicate Thanks for the feedback! We're already tracking this report/request at the linked issue. status-deferred There is no way to implement this right now, but the team wants to do it.

Comments

@rkorne
Copy link

rkorne commented Aug 24, 2023

Rubberduck version information
Version 2.5.9.6289
OS: Microsoft Windows NT 10.0.19042.0, x64
Host Product: Microsoft Office x86
Host Version: 16.0.14332.20546
Host Executable: MSACCESS.EXE

Description
During code parsing Rubberduck crashes and takes Access down. Last status is "Inspecting".
Rubberduck log shows System.OutOfMemoryExceptions

With Access 2013 there have been frequent errors "Not enough System Resources" and / or "Not enough memory", but not crashes.
And yes, it's a big project.

To Reproduce
Steps to reproduce the behavior:

  1. Open Access VBE
  2. Click on Refresh
  3. See error

Expected behavior
no crash, no error message

Screenshots
not available

Logfile
RubberduckLog.txt

Additional context
Apart from this issue I'm a happy user of Rubberduck. Wouldn't want to work without it.

@rkorne rkorne added the bug Identifies work items for known bugs label Aug 24, 2023
@rkorne
Copy link
Author

rkorne commented Aug 25, 2023

Please set this as critical, I can't work with my Access aplication at all in 2016.
Crashes with last stable as well.
Version 2.5.9.6291
OS: Microsoft Windows NT 10.0.19042.0, x64
Host Product: Microsoft Office x86
Host Version: 16.0.14332.20546
Host Executable: MSACCESS.EXE

@rkorne rkorne closed this as completed Aug 25, 2023
@rkorne rkorne reopened this Aug 25, 2023
@rkorne
Copy link
Author

rkorne commented Aug 25, 2023

closed by mistake

@Vogel612 Vogel612 added duplicate Thanks for the feedback! We're already tracking this report/request at the linked issue. status-deferred There is no way to implement this right now, but the team wants to do it. critical Marks a bug as a must-fix, showstopper issue labels Dec 23, 2023
@Vogel612
Copy link
Member

The issue in the log file is an out of memory exception. This is an unfortunate problem we keep having, since we're memory-limited by the VBE context and keeping the parsing tree of code and all inspection results in memory is ... difficult.

There is an open issue around RAM consumption where some tips can be found at #3347.

With Rubberduck3 this should be greatly alleviated because we push the state management into a separate process, which allows us to be free from the VBE memory limit :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Identifies work items for known bugs critical Marks a bug as a must-fix, showstopper issue duplicate Thanks for the feedback! We're already tracking this report/request at the linked issue. status-deferred There is no way to implement this right now, but the team wants to do it.
Projects
None yet
Development

No branches or pull requests

2 participants