Re: Trap on first use of existing Profile with seamonkey-2.35a1

On Sun, 1 May 2016 12:54:05 +0100, Peter Brown
<[email protected]> wrote:

> After installing seamonkey-2.35a1 I notice that first use of a Profile 
> with seamonkey always resulted in a C0000005 - Access Violation, 
> File:xul.dll, Cause: Attempted to read from 00000000.
>
> Every Profile worked fine with seamonkey on the 2nd attempt - and still do.
>
> Is the above common or should I be looking for the cause of a problem?

Dereferencing a null pointer is always a programming error, probably to do
with an uninitialised variable in this case.