Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
SlickEdit® / Auto generation of workspace under Ubuntu?
« Last post by command_liner on June 20, 2018, 06:30:17 pm »
We have a large code base generated with other tools, where the list of files in the code base changes pretty quickly.    The codebase is C and C++ based, and I would like to use SlickEdit more effectively.

Since the codebase changes a few times a day, the SlickEdit workspace and project  is essentially constantly out of date.  So tagging never works, and neither does navigation.
We have been living with this for a few years, but the pace of change increases, making
SE less and less useful.

Is there any way to re-generate a workspace/project every time SE starts?   
1) look in the local directory for the name of the project
2) Ignore in all cases one directory that contains temporary files
3) include all other C, C++, H files
4) possibly include a few other types of files for text search, like bash, python, tcl, perl, and some XML.

It would be good to be able to dedicate several cores to this task.  Normally SE startup and indexing is not sufficiently multi-threaded.   I could spare 8 Xeon cores and 16GB RAM if only SE could use it.     Is there any way to script this startup so that when SE starts, it is useful in this case?

This is an Ubuntu system, so please no fixes for Windows.

Thanks for any information you can provide.
22
SlickEdit® / Re: v22 memory leak?
« Last post by IkerAriz on June 20, 2018, 02:18:57 pm »
Thanks again. Looking forward to the v23 beta.

Iker

P.S. Any chance v23 can include some cache and/or allocator diagnostics to help users provide more detailed reports for issues like these?
23
SlickEdit® / Re: AccuRev support?
« Last post by Clark on June 20, 2018, 12:52:11 am »
Not yet. I took a quick look. I didn't find anything that looked like a programming language syntax with file extensions. All I see is a command line tool (accurev) which takes a bunch of command line syntax. I did see docs on a GUI tool but couldn't tell what it generates.
24
SlickEdit® / Re: v22 memory leak?
« Last post by Clark on June 19, 2018, 11:08:56 pm »

Code: [Select]
int minimap_on = 0;
_command void minimap_toggle () name_info(',') {
   if (minimap_on) {
       wfont_zoom('9');
       minimap_on = 0;
   }
   else {
      wfont_zoom('4');
      minimap_on = 1;
   }
}

Heads up. There will very likely be a minimap_toggle command on the view menu in v23. If you define a command with the same name (like above) the original minimap_toggle command will be replaced with yours. You should change the name of yours.
25
SlickEdit® / Re: v22 memory leak?
« Last post by Dennis on June 19, 2018, 10:20:33 pm »
I found another memory leak today.  Between Patrick and myself, we have cleaned up quite a few for v23.  None of them were showstoppers, but hopefully v23 will run a bit more trim than v22 for you.  I would encourage you to participate in the beta for v23 when that time rolls around.  That's about all you can do for now.
26
SlickEdit® / Re: v22 memory leak?
« Last post by IkerAriz on June 19, 2018, 07:26:17 pm »
Any other options I can pursue to help find the problem?

Iker
27
SlickEdit® / AccuRev support?
« Last post by b on June 19, 2018, 03:55:32 pm »
New job new tools.   This site uses AccuRev, but I don't see that SE supports it.  Has this ever made it onto the roadmap?  Last I saw references were back in 2007 and 2010. 
28
SlickEdit® / Re: v22 memory leak?
« Last post by Dennis on June 19, 2018, 02:42:51 pm »
Sorry, there's nothing built in that would provide any really helpful information.  We do have some allocator stats that we occasionally use in debug and unit test builds internally, but they would just provide some stats, nothing of help for tracing down where the memory is going primarily.
29
SlickEdit® / Re: v22 memory leak?
« Last post by IkerAriz on June 19, 2018, 01:10:23 pm »
Thanks for the follow up Dennis.

Any way to collect additional memory info during my tests? Eg, are there any diagnostic commands that can print the SE cache sizes and and/or allocator stats? (perhaps via a custom build?)

Thanks again,
Iker

P.S. BTW, the minimap command just toggles the zoom (I didn't use it during my tests). Here's the code:

Code: [Select]
int minimap_on = 0;
_command void minimap_toggle () name_info(',') {
   if (minimap_on) {
       wfont_zoom('9');
       minimap_on = 0;
   }
   else {
      wfont_zoom('4');
      minimap_on = 1;
   }
}

30
SlickEdit® / Re: v22 memory leak?
« Last post by Dennis on June 19, 2018, 12:43:14 am »
OK.  I've spent about a half week on this.  Good news and bad news.

1 - Good news)  I've identified, found and fixed a few memory leaks.  These fixes will be incorporated into the next release.

2 - Bad news - or Jedi mind trick)  These are not the leaks you are looking for.  It is unlikely that what I found is what brought our SlickEdit memory footprint up to 2G.  They were small leaks.

3 - resizing and drawing)  Not leaks.  We have a fairly significant line drawing cache.  You are merely filling up the cache.  The test project has a bit over 6000 lines of code, the cache holds 20000 lines before it fills and purges.  This is just using memory, not leaking it.

4 - delete and undo)  I did not observe a significant memory increase here, and the memory leak tracking software did not identify anything as leaked as a result of this test.

5 - searching) same story, yes, first time use of a feature can uptick memory somewhat, when the form is loaded the first time, etc, but no definitive leaks identified.

6 - segmenting)  We have a our own memory allocator for speed.  Like any allocator, it can fall victim to some segmenting depending on usage patterns.  Some of the memory growth you see could be segmenting, well, it will appear as growth initially, but once there is enough memory in use, the growth will level off entirely.  Note, this can happen with the system malloc() too, so there is nothing particularly wrong with our allocator, it's just faster than malloc.

7 - scrolling) see (3)

8 - caches) we have a lot of caches.  Tagging especially has a lot of caching going on.  It is one of the few things that gives you some limited control over the caches, yet, even there, there are some caches that will just grow as needed.  You can't make a setting for everything.  I have suggested ways to cut back the tagging cache earlier in this thread.

9 - your config)  You were loading a mini-map tool that I did not have access to.  Hence, this did not factor into any of my testing.

Hope this helps.  I'm still digging around for leaks, as I work.  Maybe something will surface eventually.
Pages: 1 2 [3] 4 5 ... 10