{"id":63,"date":"2020-12-21T10:12:15","date_gmt":"2020-12-21T15:12:15","guid":{"rendered":"http:\/\/blog.prestigecode.com\/?p=63"},"modified":"2020-12-21T10:12:15","modified_gmt":"2020-12-21T15:12:15","slug":"lack-of-activity","status":"publish","type":"post","link":"https:\/\/blog.prestigecode.com\/index.php\/2020\/12\/21\/lack-of-activity\/","title":{"rendered":"Lack of Activity"},"content":{"rendered":"\n<p>Hi all, <\/p>\n\n\n\n<p>I know that I haven&#8217;t posted very much the past month and I understand that this period could cause you to think I&#8217;ve abandoned things. Life has thrown me some very unexpected curveballs. <\/p>\n\n\n\n<p class=\"has-text-align-center\">Antilobby<\/p>\n\n\n\n<p>I had some issues with managing the memory leaks present in the Antilobby application, which was my main priority. I&#8217;ve gone through the source code and have tried numerous things. I even went ahead and rewrote the entire saving structure for the process tracking. That was pretty hard in itself since I tried to keep the API endpoint untouched. I did end up changing some things and making it more efficient along with the client-side saving logic. The client-side logic should now work regardless of the size of the pending save data. \ud83e\udd1e<\/p>\n\n\n\n<p>In terms of memory issues, I still don&#8217;t know a true solution for them. I have made sure that certain memory objects &#8212; when no longer needed &#8212;  are more likely to be collected by the garbage collector. I have checked threading logic and have made sure that everything inside a thread is run asynchronously and returns a boolean status code. I will also be enabling a diagnostic tool on the next update that will show current memory usage and will optionally send usage data so that I can try and see how wide-spread memory problems are. In addition to that, I want to try and add a communication section for display on the app so that I can display pertinent information and update messages.<\/p>\n\n\n\n<p>A lot of upkeep must be made in the next month so that I can be confident in the upcoming new features that will be added. I hope my testers and prospective users will be happy about these changes.<\/p>\n\n\n\n<p>Have a Happy Holiday!<\/p>\n\n\n\n<p>Sean<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Hi all, I know that I haven&#8217;t posted very much the past month and I understand that this period could cause you to think I&#8217;ve abandoned things. Life has thrown me some very unexpected curveballs. Antilobby I had some issues with managing the memory leaks present in the Antilobby application, which was my main priority. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.prestigecode.com\/index.php\/wp-json\/wp\/v2\/posts\/63"}],"collection":[{"href":"https:\/\/blog.prestigecode.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.prestigecode.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.prestigecode.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.prestigecode.com\/index.php\/wp-json\/wp\/v2\/comments?post=63"}],"version-history":[{"count":1,"href":"https:\/\/blog.prestigecode.com\/index.php\/wp-json\/wp\/v2\/posts\/63\/revisions"}],"predecessor-version":[{"id":64,"href":"https:\/\/blog.prestigecode.com\/index.php\/wp-json\/wp\/v2\/posts\/63\/revisions\/64"}],"wp:attachment":[{"href":"https:\/\/blog.prestigecode.com\/index.php\/wp-json\/wp\/v2\/media?parent=63"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.prestigecode.com\/index.php\/wp-json\/wp\/v2\/categories?post=63"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.prestigecode.com\/index.php\/wp-json\/wp\/v2\/tags?post=63"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}