Author Topic: Stack Trace - recursion too deep (also seen on SE 18)  (Read 1669 times)

skywise

  • Senior Community Member
  • Posts: 331
  • Hero Points: 10
Stack Trace - recursion too deep (also seen on SE 18)
« on: August 30, 2014, 06:13:27 am »
Win7x64
I've got a C++ file that seems to be triggering a slickcode stack trace in SE 18.0.1 dealing either with syntax coloring or autosave (I can't manipulate the window to tell).  With SE 19 beta here I decided to try it and see if it had the same problem.  It does.

Once SE gets into this state it stays locked up except for retriggering the stack dump again.  Attached is a screenshot of the dump.

Clark

  • Moderator
  • Senior Community Member
  • *
  • Posts: 4736
  • Hero Points: 382
Re: Stack Trace - recursion too deep (also seen on SE 18)
« Reply #1 on: August 30, 2014, 09:02:56 pm »
Please post a small sample file. Thanks

skywise

  • Senior Community Member
  • Posts: 331
  • Hero Points: 10
Re: Stack Trace - recursion too deep (also seen on SE 18)
« Reply #2 on: August 30, 2014, 11:54:18 pm »
I don't think I can - There seems to be a particular chunk of code that's the issue (If I navigate to that area of the code the stack occurs but I can display other areas of the file without incident)  I don't think it's the code itself but something with the tagging (which is typedefs of containers of typedefs containing more things that are typedef'd as well!)  The workspace comprises a tagging database of close to 100,000 files.

Would sending you the tagging database for the workspace plus the file do?

Clark

  • Moderator
  • Senior Community Member
  • *
  • Posts: 4736
  • Hero Points: 382
Re: Stack Trace - recursion too deep (also seen on SE 18)
« Reply #3 on: August 31, 2014, 03:14:29 pm »
Yes, that would probably work. Thanks

Your tag file will be too large to post here. I'll have support help you upload your files Tuesday (we have Monday off). If you already know how, go ahead. I don't remember.
« Last Edit: August 31, 2014, 03:17:18 pm by Clark »

skywise

  • Senior Community Member
  • Posts: 331
  • Hero Points: 10
Re: Stack Trace - recursion too deep (also seen on SE 18)
« Reply #4 on: September 04, 2014, 05:18:39 am »
Sorry for the delay!  I just uploaded the file.

When attempting to recreate it to reconfirm the steps - I managed to confirm that it does have something to do with autosaving, possibly while the syntax coloring is active.  I couldn't seem to reproduce it while just navigating the file but I added a space to an empty line to trigger the autosave and was able to trigger it.  This time, though, SE didn't lock up and I was able to copy/paste the entire stack into a text file and uploaded that along with the screenshot, the offending file and the workspace tag file (775 mb alone!)

Dennis

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2706
  • Hero Points: 413
Re: Stack Trace - recursion too deep (also seen on SE 18)
« Reply #5 on: September 04, 2014, 04:03:01 pm »
The stack trace revealed the problem.  Thanks for reporting this one.  This will be fixed.

In the future, even if you are unable to capture the stack trace directly from the Slick-C stack tool window, you can always extract it from your configuration directory/logs/stack.log.
« Last Edit: September 04, 2014, 04:05:27 pm by Dennis »