« previous next »
Pages: [1]   Go Down

Author Topic: xSchedule Memory  (Read 1633 times)

Offline colonelcline

  • Full Member
  • ***
  • Posts: 121
    • View Profile
xSchedule Memory
« on: November 23, 2019, 10:22:33 AM »
Version .64. This is the memory usage after 18 hours. I reboot daily before a show, don't know if it gets higher yet.
Logged

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: xSchedule Memory
« Reply #1 on: November 23, 2019, 07:14:13 PM »
Is that good?  I have no idea what a good number is 1.5 gig sounds like plenty should be left in the average machine.  You didn't say what the usage was in the first hour.
Logged

Offline colonelcline

  • Full Member
  • ***
  • Posts: 121
    • View Profile
Re: xSchedule Memory
« Reply #2 on: November 23, 2019, 08:22:13 PM »
I start at 6.8MB. At the end of a 6 hour show I am at 787MB. Not playing for 12 more hours I get to 1549MB. I would think that indicates a memory leak?
Logged

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: xSchedule Memory
« Reply #3 on: November 24, 2019, 10:57:52 AM »
Well 2019.65 fixes the memory leaks but some other things broke.  The memory leaks were not in our main code but being caused by compiler libraries 

Sent from my SM-G965U using Tapatalk

Logged

Offline keithsw1111

  • Administrator
  • Hero Member
  • *****
  • Posts: 2733
    • View Profile
    • Kellyville Christmas Lights
Re: xSchedule Memory
« Reply #4 on: November 24, 2019, 11:50:18 AM »
Actually 65 does not fix the leaks but I am hoping 66 will. The gcc compiler seems to be the cause of the leaks and so I am planning a move to Microsoft’s compiler.
Logged
Pages: [1]   Go Up
« previous next »