Thank you Lutz, We are not deliberately doing any XML processing at startup. So unless 4D is doing something in the background that wouldn't appear to be this issue unfortunately.
Mike -----Original Message----- From: 4D_Tech <4d_tech-boun...@lists.4d.com> On Behalf Of Epperlein, Lutz (agendo) via 4D_Tech Sent: Wednesday, November 28, 2018 8:20 AM To: 4D iNug Technical <4d_tech@lists.4d.com> Cc: Epperlein, Lutz (agendo) <lutz.epperl...@agendo.de> Subject: RE: Unusual crash / failure to start 4D Do you do some XML Processing? If yes, you should request some data from this user try to reproduce the issue with this data. Maybe there is something wrong with parsong of XML in 4D. The "<couldn't map PC to fn name>" says only 4D is not able to produce a useful stacktrace of the crash. HTH Regards Lutz > Exception caught: EXCEPTION_ACCESS_VIOLATION > Time: 2018-11-28T09:44:18 > > xercesc_3_1::DOMImplementationRegistry::getDOMImplementation > xercesc_3_1::DOMImplementationRegistry::getDOMImplementation > <couldn't map PC to fn name> > <couldn't map PC to fn name> > <couldn't map PC to fn name> > <couldn't map PC to fn name> > <couldn't map PC to fn name> > <couldn't map PC to fn name> > <couldn't map PC to fn name> > BaseThreadInitThunk ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
