Re: v13 crashes compiled and freezes

2017-05-23 Thread Kirk Brooks via 4D_Tech
Lutz, Agreed. This is a db that started back in the '90s and has an extremely complicated scheme of arrays to handle the menus. Then over the years other devs needed to change or add some functionality and, I think, rather than try to unravel what was existing added on more menu management for the

RE: v13 crashes compiled and freezes

2017-05-23 Thread Epperlein, Lutz (agendo) via 4D_Tech
My first favorite cause of crashing compiled databases is a negative array index. That's very reliable, hard to find. The best way to avoid such problems is to code defensively while handling arrays. Good luck Lutz -- Lutz Epperlein -- Agendo Gese

Re: v13 crashes compiled and freezes

2017-05-22 Thread Koen Van Hooreweghe via 4D_Tech
Hi Kirk, Just a thought. Are you sure the array as_localMen is initialized in compiled mode? In the past I've been bitten by that kind of issue. In compiled mode the array variable is always defined, but for some reason the ARRAY ...(myArray;0) line was not called. Then I found that Size of ar

Re: v13 crashes compiled and freezes

2017-05-22 Thread Kirk Brooks via 4D_Tech
OK, I resolved the freezing part - turns out there was an event handler installed that was filtering keystrokes. On Mon, May 22, 2017 at 8:19 AM, Kirk Brooks wrote: > > 1) why does 4D freeze completely? I've never seen this before. The error > dialog is shown but 4D is completely unresponsive. >