Internal Error #5333

  (#98457) Macro expanded to a local variable.  Means that VMM has died
  with a reference to an invalid or NULL memory pointer.

  (#114101) One user says that perhaps changing PRIVATE or PUBLIC variables
  to LOCAL or STATIC may affect this error.

  (#114263) This suggests that perhaps getting a macro variable: GET &mtest
  where mtest is a public, may cause the problem.  I was unable to duplicate
  this.

  () I was able to get an internal error #5333 by declaring a local array
  larger than 4096 (we'll say 'x'), then accessing an array element beyond
  x % 4096.  For instance:

  LOCAL aList[5000]
  aList[769] := "Hello World"

  (Mail: Greg Dahl [72050,650]) While using Roger Donnay's MEM50, Greg got  ~
  IE 5333 REFRESHCUR(0) after making a data change using DBEDIT().  Some
  symbol is apparently not available for DBEDIT() that should be.  Not using
  MEM50 eliminated the problem.

  (#116024) In this thread, a user was battling with a #5333 error that     ~
  kept popping up during a READ.  He solved the problem by doing a CLEAR
  GETS immediately before the first @ GET was issued.