Author Topic: Win7x64 B1: Errors observed during background tagging  (Read 4756 times)

rozum

  • Senior Community Member
  • Posts: 147
  • Hero Points: 5
Win7x64 B1: Errors observed during background tagging
« on: August 20, 2014, 11:34:22 pm »
I observed the following errors when my project files were being tagged:
Code: [Select]
Error processing file '<file path and name>': Invalid seek position
Error processing file '<file path and name>': Insufficient memory
Error processing file '<file path and name>': Database index node not valid.


Step To Reproduce
After installing Win7x64 B1,  I
  • Launched it where it migrated my 2013 settings.
  • Create a new workspace
  • Added my sources via a "add tree"
  • Closed the window.
At which point the background tagging started, after a short while, I started to observed the above mentioned errors.  After about 10 minutes SlickEdit became unresponsive and stopped responding.

Dennis

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2811
  • Hero Points: 425
Re: Win7x64 B1: Errors observed during background tagging
« Reply #1 on: August 21, 2014, 02:40:21 pm »
To help me reproduce this, what are all your settings on Tools > Options > Editing > Context Tagging ?

About how many files did you add to the project ?

Was it a wildcard project ?

What language(s) were the source files ?

rozum

  • Senior Community Member
  • Posts: 147
  • Hero Points: 5
Re: Win7x64 B1: Errors observed during background tagging
« Reply #2 on: August 22, 2014, 01:56:28 am »
Hello Dennis,
Thank you for the assistance.  Attached is an image of the requested Context Tagging settings. 

Some things to note
  • After installing V19, I immediately created a "C++ other" project and added the files via Add Tree recursive
  • The wild card was: *.cpp;*.cxx;*.h;*.hpp;*.java;*.l;*.y and was applied across multiple directories.
  • The project size was about 78,000 files of various sizes.

Additional Info
  • The first time I created this project, error occurred shortly after background tagging started.   I then uninstalled and re-installed V19 and ran the test again (migrated settings enabled from V18).  It completed this time with no errors.  In fact, it parsed all the files in about 9 minutes.  Note: SlickEdit cross referencing and displaying of the class methods "Class Tool Window" responded nicely.
  • When I uninstalled and re-installed V19 without migrating my V18 settings (default V19 values), it took about 110 minutes to parse all of the files.
  • For comparisons V18 takes 12 minutes to parse the files.

Unfortunately, at this time I am unable to recreate the original errors I had earlier reported.

rozum

  • Senior Community Member
  • Posts: 147
  • Hero Points: 5
Re: Win7x64 B1: Errors observed during background tagging
« Reply #3 on: August 22, 2014, 02:25:29 pm »
One additional performance observation.   With this huge project, V19  takes about 1 minute to become responsive when it first starts up (e.g., vs).  With V18, it is responsive immediately. 

Dennis

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2811
  • Hero Points: 425
Re: Win7x64 B1: Errors observed during background tagging
« Reply #4 on: August 25, 2014, 08:08:43 pm »
I fixed a race condition that may have been the cause of the original problem you ran into building that tag file.

SlickEdit v19 will outperform v18 with the same settings, which is what you observed (9 minutes vs. 12 minutes).  The 110 minute mark is probably just the difference between the default settings, which are a bit minimal for building a nearly 2G tag file, and your optimized settings (512M tag file cache and 4 threads).

I'll check into the startup performance issue.  Actually, I would have expected v18 to also take a while starting up with that large of a wildcard project in tow.  Did you have the same set of tool windows active with both versions?  Maybe v19 got held up filling in the Project tool window or the Open tool window?

rozum

  • Senior Community Member
  • Posts: 147
  • Hero Points: 5
Re: Win7x64 B1: Errors observed during background tagging
« Reply #5 on: August 27, 2014, 07:39:04 pm »
Hello Dennis,

I have re-verified my previous observation concerning SlickEdit V19 startup performance.

You had mentioned that possibly an Project tool or Open tool window could be contributing the 1+ minute startup delay. 

To remove these unknowns, I closed ALL of the tool windows and file buffers and then re-started SlickEdit V19.   Again, there was a 1+ minute startup delay (due to the huge project being automatically loaded in the background).

Clark

  • Moderator
  • Senior Community Member
  • *
  • Posts: 4922
  • Hero Points: 402
Re: Win7x64 B1: Errors observed during background tagging
« Reply #6 on: August 29, 2014, 02:05:37 am »
Thanks for catching this. There appears to be some work being done on the main thread which is supposed to be done on a background thread.

Dennis

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2811
  • Hero Points: 425
Re: Win7x64 B1: Errors observed during background tagging
« Reply #7 on: August 29, 2014, 04:56:24 pm »
The editor startup time problem will be fixed in Beta2.

rozum

  • Senior Community Member
  • Posts: 147
  • Hero Points: 5
Re: Win7x64 B1: Errors observed during background tagging
« Reply #8 on: September 05, 2014, 07:33:26 pm »
Hello Dennis,

With respect to the 1+ minute start-up delay.  This has been partially correct in V19B2.  The use-case that was mentioned earlier no longer exhibits a startup delay (thank you for addressing that). 

Unfortunately, if I have the Projects, Defs, Symbols, Open, Class, and Files "Tool Windows" docked and file on in a buffer window, SlickEdit V19B2 is unresponsive for 1+ minutes when it first starts up.   Again in V18, there is no delay.

Dennis

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2811
  • Hero Points: 425
Re: Win7x64 B1: Errors observed during background tagging
« Reply #9 on: September 08, 2014, 11:13:10 pm »
It looks like the time is being spent restoring the open folders in the Project tool window.  I am investigating, and will add an option to not restore the open folders in the Project tool window.

rozum

  • Senior Community Member
  • Posts: 147
  • Hero Points: 5
Re: Win7x64 B1: Errors observed during background tagging
« Reply #10 on: September 12, 2014, 03:21:51 pm »
Hello Dennis,
I know that you are looking into this issue, but I don't know if any fixes made it into Beta 4.   If they have, then unfortunately the use-case I have still has a 1+ minute delay. 

Dennis

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2811
  • Hero Points: 425
Re: Win7x64 B1: Errors observed during background tagging
« Reply #11 on: September 12, 2014, 09:18:06 pm »
The option is in Beta 4.  Go to Tools > Options... > Application Options > Auto Restore and turn off "Auto restore projects tree"

rozum

  • Senior Community Member
  • Posts: 147
  • Hero Points: 5
Re: Win7x64 B1: Errors observed during background tagging
« Reply #12 on: September 15, 2014, 02:45:05 pm »
Thank you Dennis!! I am able to open up the project nicely with the past use-cases.

Unfortunately, the start-up delay occurrs once again if I have the File Tool Windows docked when starting SlickEdit.

Note: This doesn't occur with a V18 project that mirrors the same tag project files.

Clark

  • Moderator
  • Senior Community Member
  • *
  • Posts: 4922
  • Hero Points: 402
Re: Win7x64 B1: Errors observed during background tagging
« Reply #13 on: September 15, 2014, 03:49:13 pm »
When testing v18, did you also have the Files tool window docked.

rozum

  • Senior Community Member
  • Posts: 147
  • Hero Points: 5
Re: Win7x64 B1: Errors observed during background tagging
« Reply #14 on: September 15, 2014, 07:46:52 pm »
Thank you Clark for you assistance in "debugging" this issue by suggesting looking at the docking of the File Tool Window

I was able to recreate the slowdown on V18.  Basically, if the File Tool Window is docked AND unpinned (my default configuration), there is no slow down on V18 when it starts up.  If the File Tool Window is pinned (e.g., opened), then there is a startup slow down. 

In V19, there is a startup delay in both cases.

Note
If after starting V18, I immediately expand the "files" tab by "hovering" the mouse over it.  Slickedit will become unresponsive until the File Tool Window has data to populate.