The text below is from an e-mail I tried to post last week, but for some reason it was not added to the list. I just experienced another R crash after attempting to open an existing document. The nature of the crash is that the document select window opens but rather than show the list of available documents, the spinning ball appears and I am unable to interact with R at all. I have to force it to quit and then I have to delete the "saved application state" directory and .Rhistory files. 1. Brandon: I was able to reproduce the behavior you describe when launching R by clicking on an R script. Indeed using ESC does restore the session to 'normal.' I do not generally launch R this way and the crashes I experience seem to occur when I attempt to open a new script from the "Open Document" selection in the menu bar. 2. Christoph: Have you tried deleting the ~/Library/Saved Application State/org.R-project.R.savedState/ directory? I found that I have to delete this as well as my .Rhistory file to get R to start again after the crash. 3. Simon: How does one generate a "crash log." Is this the "report" that comes up when "Force Quit" is used to terminate the R session? Also, I find that the crashes tend to occur when I try to open a script; I never get to the point where I source it. Would the system 'know" about any "possibly broken packages" before the routine is sourced?
R crashes Mac Sierra
4 messages · Barry M. Lesht, thatsanicehatyouhave at mac.com, Christoph Napierala
On Jan 30, 2017, at 12:56 PM, Barry M. Lesht <blesht at gmail.com> wrote:
3. Simon: How does one generate a "crash log." Is this the "report" that comes up when "Force Quit" is used to terminate the R session? Also, I find that the crashes tend to occur when I try to open a script; I never get to the point where I source it. Would the system 'know" about any "possibly broken packages" before the routine is sourced?
These are the text of the "<app name> quit unexpectedly" dialogs that come up when a program crashes. The window is filled with details of the crash. Don't copy/paste this text though. Whenever you see such a crash, a crash log file is created in this folder, e.g. /Users/demitri/Library/Logs/DiagnosticReports/R_2017-01-05-182715_iMac.crash Send this as a file (for ease of use for the developer!). With this file, the developer can find out the exact line of code the program crashed. Cheers, Demitri
Thank you, Demitri!
On Mon, Jan 30, 2017 at 12:11 PM, <thatsanicehatyouhave at mac.com> wrote:
On Jan 30, 2017, at 12:56 PM, Barry M. Lesht <blesht at gmail.com> wrote:
3. Simon: How does one generate a "crash log." Is this the "report"
that
comes up when "Force Quit" is used to terminate the R session? Also, I find that the crashes tend to occur when I try to open a script; I never get to the point where I source it. Would the system 'know" about any "possibly broken packages" before the routine is sourced?
These are the text of the "<app name> quit unexpectedly" dialogs that come up when a program crashes. The window is filled with details of the crash. Don't copy/paste this text though. Whenever you see such a crash, a crash log file is created in this folder, e.g. /Users/demitri/Library/Logs/DiagnosticReports/R_2017-01- 05-182715_iMac.crash Send this as a file (for ease of use for the developer!). With this file, the developer can find out the exact line of code the program crashed. Cheers, Demitri
Dear Barry Thanks a lot for your input - so far it worked! Excellent Kind regards Christoph
On 30.01.17 18:56, Barry M. Lesht wrote:
The text below is from an e-mail I tried to post last week, but for some reason it was not added to the list. I just experienced another R crash after attempting to open an existing document. The nature of the crash is that the document select window opens but rather than show the list of available documents, the spinning ball appears and I am unable to interact with R at all. I have to force it to quit and then I have to delete the "saved application state" directory and .Rhistory files. 1. Brandon: I was able to reproduce the behavior you describe when launching R by clicking on an R script. Indeed using ESC does restore the session to 'normal.' I do not generally launch R this way and the crashes I experience seem to occur when I attempt to open a new script from the "Open Document" selection in the menu bar. 2. Christoph: Have you tried deleting the ~/Library/Saved Application State/org.R-project.R.savedState/ directory? I found that I have to delete this as well as my .Rhistory file to get R to start again after the crash. 3. Simon: How does one generate a "crash log." Is this the "report" that comes up when "Force Quit" is used to terminate the R session? Also, I find that the crashes tend to occur when I try to open a script; I never get to the point where I source it. Would the system 'know" about any "possibly broken packages" before the routine is sourced? [[alternative HTML version deleted]]
_______________________________________________ R-SIG-Mac mailing list R-SIG-Mac at r-project.org https://stat.ethz.ch/mailman/listinfo/r-sig-mac