Skip to content
Prev 12203 / 15075 Next

segfault on R v. 3.4.1

On 14/09/2017 12:13 PM, James Plante wrote:
In your case, it means that some part of the code is trying to refer to 
a nonexistent memory address.  This is certainly a bug somewhere or other.

 From the traceback you posted, this appears to happen when R is trying 
to load the compiled library of some package.  I don't see information 
on what package that is.

If it is a contributed package, the bug likely lies there.  You might be 
able to see this by going into the console and running

R --vanilla

which will load R with reduced startup code -- an old workspace won't be 
loaded, etc.  If that works, then you can gradually add back the things 
you usually use (see ?Startup for the startup process) until you find 
what triggers the problem.

If that fails, then the problem is likely with R, or some basic part of 
your system.  Four years old doesn't seem old, but it's long enough for 
hardware problems to develop.

Duncan Murdoch