From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.182.4.7 with SMTP id g7mr1478483obg.36.1413245178985; Mon, 13 Oct 2014 17:06:18 -0700 (PDT) X-Received: by 10.182.165.36 with SMTP id yv4mr284obb.30.1413245178893; Mon, 13 Oct 2014 17:06:18 -0700 (PDT) Path: border1.nntp.dca1.giganews.com!nntp.giganews.com!news.glorb.com!uq10no10201764igb.0!news-out.google.com!rp1ni27119igb.0!nntp.google.com!uq10no10201743igb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Mon, 13 Oct 2014 17:06:18 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=66.176.73.77; posting-account=yiWntAoAAAC1KqC_shmxJYv07B9l6LNU NNTP-Posting-Host: 66.176.73.77 References: <13fb4505-4abd-4d5b-b18d-d05aa0a4dcb9@googlegroups.com> <32414aa2-3a0f-41fc-aef3-d8db709aacfc@googlegroups.com> <0b5ee58b-2d2d-4394-8215-0fa5d1a4740e@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <5bf99c39-20f1-4fe3-9601-5c4d00598d7b@googlegroups.com> Subject: Re: Gnoga Latest Updates From: David Botton Injection-Date: Tue, 14 Oct 2014 00:06:18 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Xref: number.nntp.giganews.com comp.lang.ada:189742 Date: 2014-10-13T17:06:18-07:00 List-Id: Interesting... In general I've had a lot of strange interactions with taski= ng and AWS events. If the Connection_Holder_Type (a protected type, basic no resetting semipho= re) is released from with the AWS websocket event it does not release the h= olds in side the main application. It seems a bug to me with GNAT and/or AWS but I don't have the time now to = spend on a reproducer, etc. although easy enough to reproduce using just Gn= oga.=20 For person future refernce as of git commit e5cfd8019249a0fe9ffbf3085861e90= b4b75c3fd Based on the current implementation, it should already be working, ie. Mess= age_Loop will end on break of connection in a Singleton and any clean up ca= n be done and the app exit. Officially that is how it should and God willin= g soon enough (with a work around) will work. On_Destroy shouldn't be needed to end the app (and in fact would be too lat= e), but could be used for clean up as will fire on finalization of the Main= _Window. David Botton