AFNI Message Board

Dear AFNI users-

We are very pleased to announce that the new AFNI Message Board framework is up! Please join us at:

https://discuss.afni.nimh.nih.gov

Existing user accounts have been migrated, so returning users can login by requesting a password reset. New users can create accounts, as well, through a standard account creation process. Please note that these setup emails might initially go to spam folders (esp. for NIH users!), so please check those locations in the beginning.

The current Message Board discussion threads have been migrated to the new framework. The current Message Board will remain visible, but read-only, for a little while.

Sincerely, AFNI HQ

History of AFNI updates  

|
February 07, 2020 12:38PM
After changing those two variables, running the anova, I still encountered the same error. A little over 30 minutes to get to slice 256 before seeing:

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

Traceback:
1: write.c.AFNI(filename, dset = brk, label = label, space = space, note = note, origin = origin, delta = delta, orient = orient, idcode = idcode, defhead = defhead, verb = verb, maskinf = maskinf, scale = scale, addFDR = addFDR, statsym = statsym, view = view, com_hist = com_hist, type = type, TR = TR, overwrite = overwrite)
2: write.AFNI(lop$outFN, out, brickNames, defhead = head, idcode = newid.AFNI(), com_hist = lop$com_history, statsym = statsym, addFDR = 1, type = "MRI_short", overwrite = lop$overwrite)
An irrecoverable exception occurred. R is aborting now ...
Segmentation fault

I should note before I was encountering this error, I was getting the "vector memory limit reached" but when i changed the R_MAX_VSIZE variable to 200Gb, and I no longer got that error. I'm thinking that the memory limit set by R actually includes both the total memory used and the compressed memory, and when the final slice is done, the memory and compressed memory combined go over 200 (meanwhile the memory pressure visual doesnt indicate anything is having a problem). Im on a mac, high Sierra, 32gb DDR4, 4.2 GHz Intel Core i7. Any ideas?
Attachments:
open | download - slice256_memory.jpg (969 KB)
Subject Author Posted

*** caught segfault *** address... cause 'memory not mapped'

defenderfer February 07, 2020 09:11AM

Re: *** caught segfault *** address... cause 'memory not mapped'

rick reynolds February 07, 2020 09:27AM

Re: *** caught segfault *** address... cause 'memory not mapped'

defenderfer February 07, 2020 10:28AM

Re: *** caught segfault *** address... cause 'memory not mapped' Attachments

defenderfer February 07, 2020 12:38PM

Re: *** caught segfault *** address... cause 'memory not mapped'

rick reynolds February 07, 2020 12:55PM

Re: *** caught segfault *** address... cause 'memory not mapped'

defenderfer February 07, 2020 02:42PM

Re: *** caught segfault *** address... cause 'memory not mapped'

rick reynolds February 07, 2020 06:55PM

Re: *** caught segfault *** address... cause 'memory not mapped'

defenderfer February 10, 2020 11:20AM

Re: *** caught segfault *** address... cause 'memory not mapped'

rick reynolds February 11, 2020 09:03AM

Re: *** caught segfault *** address... cause 'memory not mapped'

defenderfer February 11, 2020 11:47AM