I have had a similar experience with schemas that imported 10 or so schemas. When I reduced the amount of code and commented out 5 import elements, the Saxon-EE 9.4.0.3 for xsd1.1 validator worked and the CPU dropped down to minimum usage. Since XSD allows schemas to call each other, I would not be surprised if this was part of the problem. I am running the latest upgrade of the 64 bit version of the oXygen editor. Bob Leif -----Original Message----- From: oxygen-user-bounces@oxygenxml.com [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of David Sewell Sent: Wednesday, August 08, 2012 11:36 AM To: oxygen-user@oxygenxml.com Subject: [oXygen-user] Any way to recover in-memory files? oXygen users, I'm running oXygen 13.2 on a Mac. I was in the middle of editing a long XML file and did a global search-and-replace that had the effect of creating ill-formed XML. Now oXygen is spinning endlessly, running one core at 100% CPU, apparently trying to parse the file. I was also editing some XQuery code in a couple of tabs that I had not saved to disk yet. oXygen won't let me open those tabs as it is trying to complete its Find/Replace. Any ideas on how I can retrieve the code? If I force-quit the oXygen process, would the data be written anywhere that it could be retrieved? this is not mission-critical but if there is a way to retrieve the content it would be nice. DS -- David Sewell, Editorial and Technical Manager ROTUNDA, The University of Virginia Press PO Box 400314, Charlottesville, VA 22904-4314 USA Email: dsewell@virginia.edu Tel: +1 434 924 9973 Web: http://rotunda.upress.virginia.edu/ _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user