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 02:42PM
I know, the activity monitor is a bit confusing. The "Memory" column reflects the total memory used (memory plus compressed memory). Technically, the amount of ram (of 32gb) being used at any given moment is at the bottom of the screen where it says "memory used". Sometimes it gets close to 32, but never seems to reach 32. And the "memory pressure" gauge doesnt show much happening there, so its hard for me to believe that im having a memory problem. Ill try making a smaller test file with fewer participants and see what happens.
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