XmlFileErrorLog creates empty files when disk is full

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use XMLErrorLog
2. Point it to a drive that is full
3. Provoke an error that should be logged

What is the expected output? What do you see instead?
I would expect no files to be created.
Instead I see empty xml files. The problem is that these are then treated as 
malformed xml and this results in the elmah page being unable to open untill 
the files are deleted. 

What version of the product are you using? On what operating system?
1.2.14706.955
Windows 7 Ultimate sp1 x64

Please provide any additional information below.

Original issue reported on code.google.com by hedegaar...@gmail.com on 3 Apr 2014 at 10:08

[GoogleCodeExporter]

Original comment by azizatif on 7 Apr 2014 at 1:38

• Changed title: XmlFileErrorLog creates empty files when disk is full
• Changed state: Accepted
• Added labels: Component-Persistence, Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

This issue has been migrated to:
https://github.com/elmah/Elmah/issues/356
The conversation continues there.
DO NOT post any further comments to the issue tracker on Google Code as it is 
shutting down.
You can also just subscribe to the issue on GitHub to receive notifications of 
any further development.

Original comment by azizatif on 25 Aug 2015 at 8:26