Re: v13 crashes compiled and freezes

[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 their
purposes. This resulted in a very complex web which I upset by making a
change unrelated to menus at all. I'm going to take a little time and see
if all of that is even necessary any longer. The tools available for menu
management are much better now. When I found myself trying to pull a tech
note out of ACI FTP from 1996 so I could read up on how menus were managed
back then I realized I may be going about this the wrong way.

On Tue, May 23, 2017 at 12:10 AM, Epperlein, Lutz (agendo) via 4D_Tech <
4d_tech@lists.4d.com> wrote:

> 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.
>

-- 
Kirk Brooks
San Francisco, CA
===

*The only thing necessary for the triumph of evil is for good men to do
nothing.*

*- Edmund Burke*
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

RE: v13 crashes compiled and freezes

[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 Gesellschaft für politische Planung mbH
Köpenicker Str. 9
10997 Berlin
http://www.agendo.de/
--


**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: v13 crashes compiled and freezes

[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 array (myArray) returned a huge 
number. So 4D thought there were lots of elements (no range check error raised) 
but the memory was not reserved because there should have been none. Result: 
crash when trying to access the none existent array elements.

HTH
Koen

Op 22-mei-2017, om 17:19 heeft Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com> 
het volgende geschreven:

> $j:=Size of array(as_localMen)




Compass bvba
Koen Van Hooreweghe
Kloosterstraat 65
9910 Knesselare
Belgium
tel +32 495 511.653

**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: v13 crashes compiled and freezes

[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.
>
> --
Kirk Brooks
San Francisco, CA
===

*The only thing necessary for the triumph of evil is for good men to do
nothing.*

*- Edmund Burke*
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**