Re: Upgrading 32-bit Mac apps to 64-bit
Jon Ogden <[email protected]>
| Newsgroups | gmane.comp.lang.realbasic.user |
|---|---|
| Message-ID | <[email protected]> |
Methods aren't objects. It's an instance of an object or some reference to an object. Sent from my iPhone > On May 21, 2017, at 3:31 PM, Paul Young <[email protected]> wrote: > > Jon, > > Would an instance of a method cause this? If so, how would one close/cancel/etc. the instance? > > Paul > > > > > > >> On May 21, 2017, at 3:07 PM, Jon Ogden <[email protected]> wrote: >> >> Paul, >> >> You can always look in the docs. But there is something in an object of code that is in your window or app that is not closing before the app tries to close. Make sure you have no circular references and make sure that all of your things like AddHandler references are undone. Some reference to something is being left open. >> >> Jon >> >> Sent from my iPhone >> >>> On May 21, 2017, at 1:59 PM, Paul Young <[email protected]> wrote: >>> >>> Nothing significant to report after: >>> >>> a. making sure all integers are Int64 >>> >>> b. making sure all other Windows are closed before running the Window1.Close code >>> >>> c. stopping the one timer that is running in Window1 (Timer1.Mode = 0) >>> >>> d. stepping through the code (no problems until Window1 is closed and then, occasionally, an exception is thrown) >>> >>> Is there an article available that summarizes changes to make to 32-bit code before compiling to 64-bit code? >>> >>> Thanks in advance. >>> >>> Paul Young, CSoM >>> >>> >>> >>> >>> >>> >>>> On May 20, 2017, at 1:09 PM, Jon Ogden <[email protected]> wrote: >>>> >>>> Thinking about this further, this is my educated guess. >>>> >>>> The 32 bit framework shut things down in a certain order and you relied on that in your code to close out all your objects. The 64 bit framework is handling all that differently so the order you relied on before is now different. So some object is calling on or relying on some other object that is already closed. When that happens things crash. >>>> >>>> You'll just have to step through things to figure it out. Don't rely on the framework doing things in a specific order. >>>> >>>> Sent from my iPhone >>>> >>>>> On May 20, 2017, at 12:01 PM, Jon Ogden <[email protected]> wrote: >>>>> >>>>> You have something in your code that is not truly 64 bit compatible. Maybe you are using a 32 bit integer some place where you should be using 64 bit. >>>>> >>>>> There's not much that one can tell from that. But it looks to me like some object isn't closing correctly. >>>>> >>>>> You don't have to do much to make 64 bit work. But you do have to adjust some things. >>>>> >>>>> I would try stepping through the code when closing your app to find the thing causing the problem. It has likely always been there but Xojo and the 32 bit framework was a little more forgiving. >>>>> >>>>> Sent from my iPhone >>>>> >>>>>> On May 20, 2017, at 11:00 AM, Paul Young <[email protected]> wrote: >>>>>> >>>>>> I am using a MacBook Pro running macOS Sierra Version 10.12.4 to upgrade my first six 32-bits Mac apps to 64-bits. >>>>>> >>>>>> Each of the six apps worked fine when compiled for 32-bits. >>>>>> >>>>>> Because my Mac Xojo license expired late last year, I used Xojo 2017 Release 1.1 to test the apps in the IDE for 64-bits and then compiled them for 64-bits using Xojo 2016 Release 3. >>>>>> >>>>>> Launching each app twenty times, I recorded an exception upon close 20% to 50% of the time. >>>>>> >>>>>> The Console log shows: “Service exited dur to signal: Segmentation fault: 11 sent by exc handler (0). >>>>>> >>>>>> Can someone tell me in simple English what this means? >>>>>> >>>>>> Thanks in advance. >>>>>> >>>>>> Paul Young, CSoM > > _______________________________________________ > > Xojo forum: > > https://forum.xojo.com/ _______________________________________________ Xojo forum: https://forum.xojo.com/