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

The very1st use of indent (on the complete (medium) project) hangs ! #5712

Open
micniv opened this issue Apr 2, 2021 · 2 comments
Open

The very1st use of indent (on the complete (medium) project) hangs ! #5712

micniv opened this issue Apr 2, 2021 · 2 comments
Labels
bug Identifies work items for known bugs

Comments

@micniv
Copy link

micniv commented Apr 2, 2021

Rubberduck version information
The info below can be copy-paste-completed from the first lines of Rubberduck's log or the About box:
Version 2.5.1.5758
OS: Microsoft Windows NT 10.0.19042.0, x64
Host Product: Microsoft Office 2013 x86
Host Version: 15.0.5267.1000
Host Executable: MSACCESS.EXE

Description
this project has several years. Indentation was running smart with SmartIndent.
Only I have to use now Access 2013 32 bits. And I can't install SmartIndent on that product.
So I 'm trying RubberducK. But bad luck to indent with rubberduck 👍
The first time, I can only indent the whole project and after several object, it hangs definitely.
"mémoire insuffisante pour exécuter cette tache ..." and no way than to loose my last 15 min of work.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
I just wanted the indentation job were completed ... and fast !

Additional context
My pc is a new one : DELL XPS 15 with 16 Go RAM

@micniv micniv added the bug Identifies work items for known bugs label Apr 2, 2021
@daFreeMan
Copy link
Contributor

daFreeMan commented Apr 2, 2021

Please go to the Rubberduck menu in the VB Editor, then select "About". In the dialog box that pops up, click the "View log in File Explorer" link (the bottom link in the top left box, in case yours is translated into a different language). Edit your original question and drag the RubberduckLog.txt file from the File Explorer window into your post. Being able to see the exact error trace will help immensely.

@retailcoder
Copy link
Member

Linking #3347

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
Projects
None yet
Development

No branches or pull requests

3 participants