Here's another separate issue that typically causes fault on memory access to website-influenced memory access: http://lcamtuf.coredump.cx/ffoxdie3.html This is separate from the previously presented example (which, remarkably, also had a tendency to trigger an unrelated call stack overflow due to XML parsing glitch on some platforms, which caused some confusion - my bad). Note that because it depends on timing more heavily, it may not work in the first shot on all computers (though it should). /mz
