|
The following movie demonstrates all of the XML parser bugs using a number of different tests. Download the .dir file and create a projector to test on your system.
Disclaimer:
Don't run this test if you have unsaved data or are unsure about what you are doing. Since you are trying to initiate a large memory leak, there is an increased chance that your system will crash as a result. This is an extreme case that should not normally happen, but I take no responsibility for anything that occurs as a result of you running this test on your system. I assume that if you are running this test that you know what you are doing and are using it responsibly.
About the test movie
The tests do not report a pass/fail results: you need to run it for a while to see whether memory usage is normal or not. Don't rely on Director's freeBytes and freeBlock information to tell whether memory really is leaking or not. Run the Windows Performance Monitor (in Task Manager), OSX Activity Monitor or similar. This will give a true picture of Director's memory usage. FreeBytes and freeBlock are unreliable: they tend to give totally different results on different platforms/versions. They can be a good visual indicator, provided you double-check using something else too. If the memory usuage appears to be creeping up and never going back down then that is a good indicator of a leak. Small fluctuations that return to a normal level after a short time are perfectly normal behaviour in keeping with the way Director's memory management operates. After you've been running the test for a while it should be clear whether there is a leak or not. Do not run any other applications while running the test as that could affect the result.
Download the test movie:
Article Information
Published: 2004.08.04
Updated: 2005.02.12
Author: Robert Tweed
| 
