Junk <junk(a)therobinsonfamily.net> writes:
It also might be something much more mundane such as a bug in the
browser which occurs when you have 100+ tabs open and tries to write to
a misaddressed memory region.
It may well be some malloc()-like routine returning 0, saying "no more
memory for you buddy" and the code blindly dereferencing that value and
causing a write to the 0-page. It is a common error with sloppy coders.
-wolfgang
--
g+:
https://plus.google.com/114566345864337108516/about