Skip to content

caught segfault *** 'memory not mapped` -An irrecoverable exception occurred. R is aborting now ... #344

@zackarno

Description

@zackarno

I have GHA running on ubuntu that returns this error:

*** caught segfault ***
address 0x1f1000160, cause 'memory not mapped'

Traceback:
 1: curl_fetch_memory(smtp_server, handle = h)
 2: curl::send_mail(mail_from = unname(from), mail_rcpt = unname(c(to,     cc, bcc)), message = email_qp, smtp_server = paste0(credentials$host,     ":", credentials$port), use_ssl = credentials$use_ssl %||%     TRUE, verbose = verbose, username = credentials$user, password = credentials$password,     login_options = login_options, ...)
 3: smtp_send(email = knitted_email, from = from_email,     to = df_email_receps$email[1], subject = ifelse(EMAIL_LIST !=         "full_list", paste0("TEST: ", email_txt$subj), email_txt$subj),     credentials = email_creds)
An irrecoverable exception occurred. R is aborting now ...
/home/runner/work/_temp/b0e91a74-b79a-4a57-8259-5[52](https://github.com/OCHA-DAP/ds-aa-lac-dry-corridor/actions/runs/13321702421/job/37207437114#step:10:53)0b923665c.sh: line 1:  8041 Segmentation fault      (core dumped) Rscript ./src/monitoring_2025/update_activation_status.R

Oddly it runs fine locally. Additionally I can get the GHA to run successfully when i toggle one of the date filters for the data which seems highly unrelated, but below you can see two runs and there different results. One was successful, whereas the other produced the above error. Locally I can set the RUN_DATE_USE env var either way and the email sends just fine.

run that worked

and the parameters set as:

Image

run that failed

and the screenshot below showing the only change that was made to the env var (RUN_DATE_USE) set as workflow parameter (no change to code)

Image

to make the issue even more confusing I can get the GHA runner to send the email successfully w/ the offending RUN_DATE_USE parameter (that causes failure only on runner) , if I turn off our in house ggtheme package.

issue seems like it could be relate to the below, but hard to say

#272
#270

My colleague is getting the error described in #19 when running locally as well - I've also gotten this, but it seems to have gone away locally, but perhaps something similar manifesting in the runner.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions