Re: destroystack wrong behavior...
Hi all, Thanks to all for your suggestions. I've found a solution to this question. not sure if it is completely resolved, but seems to work quite well. So, better share in the hope it will help few of you... I've changed the filename of my stack, that's it ! then the name and the filename properties are different, which was not the case before. I leave the explanations to the IDE gurus :) ps: running the stack with Suspend Development Tools on, was also working before. Regards, Thierry ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: destroystack wrong behavior...
Le 19 mai 2010 à 23:05, Malte Pfaff-Brill a écrit : Thierry, Hello Malte, does your stack have any substacks that are still open? Rev can not destroy it in that case. Yes, one substack and sometimes it's visible, sometimes not visible. Then, the mainstack is closed, but still in memory. But it's not my problem right now. ( I've pass to this one too, especially when the substack is hidden ) Do you reference to it with a filePath? - Will be reopened each time you reference to it then. I did the test with One stack + 1 substack ( which does nothing ) So, where can I reference it with a filePath ? I guess it's not for my case. Does it carry an external that is still used? - Rev won´t destroy it then AFAIK That's probably the point. Can someone give a definition of still in use ? In all the externals I made, I always build a sort of ResetExternalFunction to do all kinds of reset, freeing buffers,... But nowhere I've seen any information about closing/unloading an external As for the last 10 years, starting from Metacard on Unix, then using mostly Metacard, then using kRev, never had one of this problem. Hmm, and I've make almost 50 externals mainly for specific customer applications and few to be used within the Rev IDE. So, I'm not that familiar with the Rev IDE tricks. Other than those cases, I have never seen destroystack fail. Different ways of coding and working with Rev... Maybe you were lucky or maybe I'm not :) Another point: this reminds me one thread on this list about someone who couldn't start an external. I guess/feel that his problem could be that his stack was still in memory, and when he restarted it, the normal process of loading the external didn't work because the stack was already in memory. My 2 cents. Thanks to all for your suggestions. Regards, Thierry ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
RE: destroystack wrong behavior...
Thierry wrote: Another point: this reminds me one thread on this list about someone who couldn't start an external. I guess/feel that his problem could be that his stack was still in memory, and when he restarted it, the normal process of loading the external didn't work because the stack was already in memory. There is an issue here. The issue involves destroyStack and externals and memory usage both in the IDE and in standalones on Windows (probably on Mac also, but I was never able to positively confirm it on Mac). This issue is if you start a stack that uses an external that leaks memory, like revBrowser (revBrowser itself doesn't leak, but the browser control that it uses does). The known way to release the leaked memory is to close the external. The way to release the external is to destroy the stack that opened the external. However, after destroying the stack (and there is some question as to whether the stack was actually destroyed or not), the fact is that the memory is not released. This would indicate that the stack was not destroyed and the external is still in memory. In any case, the only way to release the memory is to close the IDE or standalone itself. My understanding is that this is a big architectural change that will be addressed as part of other architectural changes in the future. Aloha from Hawaii, Jim Bufalini ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: destroystack wrong behavior...
Hi Thierry, Yes, I am having the same problem. Once in a while, even after explicitly deleting a stack with the delete command, the stack still pops up somehow. I think this is due to the compexity of the IDE. Probably, the IDE team has used the long ID of a stack in several places, instead of the short name of the stack. If this reference to the long ID of a stack stays in memory, then the IDE will be able to find the stack even after it has been removed from memory. I don't think there is a quick solution for this problem, besides quitting and re-startingi RunRev. Of course, it is also possible that the long ID of a stack is still available in one of your own stacks. You might want to make sure that these references are not there. -- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering Homepage: http://economy-x-talk.com Twitter: http://twitter.com/xtalkprogrammer Economy-x-Talk is always looking for new projects. Contact me for a quote http://economy-x-talk.com/contact.html Download Clipboard Link http://clipboardlink.economy-x-talk.com and share the clipboard of your computer over the local network. On 19 mei 2010, at 11:34, Thierry D. wrote: Hi all, from time to time, in Rev IDE ( 4.0 MacOS ) when closing a stack, the stack is still in memory, seen in the Application browser too. DestroyStack and DestroyWindow are set properly ! and Yes, I refresh the application browser. It had happened few times during my developments, and never I could find a solution ? More, sometimes, it works again after a while without being able to know why. Does it sound familiar to someone and any idea what could cause this wrong behavior ? Regards, Thierry ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: destroystack wrong behavior...
Hi Thierry, Yes, I am having the same problem. Once in a while, even after explicitly deleting a stack with the delete command, the stack still pops up somehow. Thanks Mark I'm not alone ! Half the suffering is gone :) I think this is due to the compexity of the IDE. Probably, the IDE team has used the long ID of a stack in several places, instead of the short name of the stack. If this reference to the long ID of a stack stays in memory, then the IDE will be able to find the stack even after it has been removed from memory. As I have only one stack and a substack within can't see the long-id-stack virus from my side. Agree ? I don't think there is a quick solution for this problem, besides quitting and re-starting RunRev. Hmm, so I have to put a Red Banner for my customers :( Of course, it is also possible that the long ID of a stack is still available in one of your own stacks. You might want to make sure that these references are not there. I'll check again... Regards, Thierry Hi all, from time to time, in Rev IDE ( 4.0 MacOS ) when closing a stack, the stack is still in memory, seen in the Application browser too. DestroyStack and DestroyWindow are set properly ! and Yes, I refresh the application browser. It had happened few times during my developments, and never I could find a solution ? More, sometimes, it works again after a while without being able to know why. Does it sound familiar to someone and any idea what could cause this wrong behavior ? Regards, Thierry ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: destroystack wrong behavior...
Thierry D. wrote: Hi all, from time to time, in Rev IDE ( 4.0 MacOS ) when closing a stack, the stack is still in memory, seen in the Application browser too. DestroyStack and DestroyWindow are set properly ! and Yes, I refresh the application browser. It had happened few times during my developments, and never I could find a solution ? More, sometimes, it works again after a while without being able to know why. Does it sound familiar to someone and any idea what could cause this wrong behavior ? What happens if you type into the message box: delete stack main stack Does it go away then? (Make sure you specify the mainstack, not the substack.) -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: destroystack wrong behavior...
Le 19 mai 2010 à 19:59, J. Landman Gay a écrit : What happens if you type into the message box: delete stack main stack Does it go away then? (Make sure you specify the mainstack, not the substack.) Hmmm, as soon as I sent my email to this list, it starts to work again :) and without changing anything in my stack ! So, I'll try this later... Regards, Thierry ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: destroystack wrong behavior...
What happens if you type into the message box: delete stack main stack Does it go away then? (Make sure you specify the mainstack, not the substack.) Yes, it does! However, if you have saved the stack it will still exist where it has been saved. All that DELETE STACK does is remove it completely from the memory of the IDE. ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: destroystack wrong behavior...
Richmond Mathewson wrote: What happens if you type into the message box: delete stack main stack Does it go away then? (Make sure you specify the mainstack, not the substack.) Yes, it does! However, if you have saved the stack it will still exist where it has been saved. All that DELETE STACK does is remove it completely from the memory of the IDE. Right. But that's what he wanted. The issue is whether or not destroystack is working as it's supposed to. I haven't seen any problems with it but since two people think they have, that's what's under investigation. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: destroystack wrong behavior...
Been there as well, came to a little fix if you can call that a fix, instead of closing the stack try something along the lines of: delete stack myStack This will really take it out of the memory, so these days, I close and then I delete or vice versa... On Wed, May 19, 2010 at 6:34 AM, Thierry D. th.do...@gmail.com wrote: Hi all, from time to time, in Rev IDE ( 4.0 MacOS ) when closing a stack, the stack is still in memory, seen in the Application browser too. DestroyStack and DestroyWindow are set properly ! and Yes, I refresh the application browser. It had happened few times during my developments, and never I could find a solution ? More, sometimes, it works again after a while without being able to know why. Does it sound familiar to someone and any idea what could cause this wrong behavior ? Regards, Thierry ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution -- http://www.andregarzia.com All We Do Is Code. ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: destroystack wrong behavior...
On 19/05/2010 22:19, J. Landman Gay wrote: Richmond Mathewson wrote: What happens if you type into the message box: delete stack main stack Does it go away then? (Make sure you specify the mainstack, not the substack.) Yes, it does! However, if you have saved the stack it will still exist where it has been saved. All that DELETE STACK does is remove it completely from the memory of the IDE. Right. But that's what he wanted. The issue is whether or not destroystack is working as it's supposed to. I haven't seen any problems with it but since two people think they have, that's what's under investigation. Is this chap running on Win, Mac or Linux? Unfortunately I hosed my Linux box (trying to be too clever for my own good; nothing new) and am, right now, in the process of doing a complete reinstall. But can try this in Windows directly and in Linux in about 90 minutes. ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: destroystack wrong behavior...
Le 19 mai 2010 à 21:38, Richmond Mathewson a écrit : On 19/05/2010 22:19, J. Landman Gay wrote: Richmond Mathewson wrote: What happens if you type into the message box: delete stack main stack Does it go away then? (Make sure you specify the mainstack, not the substack.) Yes, it does! As I said in the last email, sometimes it works just the way is has, sometimes not. All that DELETE STACK does is remove it completely from the memory of the IDE. Right. But that's what he wanted. The issue is whether or not destroystack is working as it's supposed to. I haven't seen any problems with it but since two people think they have, that's what's under investigation. I don't really mind from my side, but it's annoying for those I'm sending my work... One problem out of this is when you start again the stack, the init processing ( depending on my own design doesn't work correctly then. ) and from the user's point of view it just doesn't work ! This is the real side effect for me :( So, I have to investigate this and make a consistent workaround. Maybe it's because of my code, maybe not... but I need to fix it. Is this chap running on Win, Mac or Linux? Hey , Richmond ! I said on Mac with Rev 4.0 :) Regards, Thierry ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: destroystack wrong behavior...
Le 19 mai 2010 à 21:34, Andre Garzia a écrit : Been there as well, came to a little fix if you can call that a fix, instead of closing the stack try something along the lines of: delete stack myStack This will really take it out of the memory, so these days, I close and then I delete or vice versa... So, we are at least 3 to have experienced it ! Sounds a good one. I'll try it for a while and see... Regards, Thierry ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: destroystack wrong behavior...
Thierry, does your stack have any substacks that are still open? Rev can not destroy it in that case. Do you reference to it with a filePath? - Will be reopened each time you reference to it then. Does it carry an external that is still used? - Rev won´t destroy it then AFAIK Other than those cases, I have never seen destroystack fail. All the best, Malte___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: destroystack wrong behavior...
Malte Pfaff-Brill wrote: Thierry, does your stack have any substacks that are still open? Rev can not destroy it in that case. Do you reference to it with a filePath? - Will be reopened each time you reference to it then. Does it carry an external that is still used? - Rev won´t destroy it then AFAIK Other than those cases, I have never seen destroystack fail. Right. Other things that prevent a stack closing are drivers that haven't been closed (i.e., revSpeech, etc.) and any pending messages that haven't been cancelled. Externals aren't a problem, stacks will still close when using those. So to ensure that a stack is really removed from memory when closing: 1. Destroystack must be set to true 2. Substacks must be closed 3. Pending messages must be cancelled 4. Any open drivers must be closed -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: destroystack wrong behavior...
4. Any open drivers must be closed How to tell what are the open drivers? Is there a commad like openStacks for drivers? BTW, I too've suffered this destroystack wrong behavior, always shrugging it off as something of my own doing rather than Rev's. Something I'm even more convinced of after reading Jacqueline's warning to make sure everything and the kitchen sink is truly closed. -- Nicolas Cueto ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
