Author Topic: v22 memory leak?  (Read 5147 times)

Dennis

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2499
  • Hero Points: 363
Re: v22 memory leak?
« Reply #45 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.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 4479
  • Hero Points: 343
Re: v22 memory leak?
« Reply #46 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.

IkerAriz

  • Senior Community Member
  • Posts: 140
  • Hero Points: 6
Re: v22 memory leak?
« Reply #47 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?