xpaoom(7)

💖 xpaoom — bestie, what even happens when XPA runs out of memory?? 💖

okay so real talk: this is a page from the SAORD Documentation collection, it lives in section 7 of the manual, and it's here to answer one extremely specific, extremely dramatic question. 🫶

✨ NAME ✨

Xpaoom — what happens when XPA runs out of memory? 😭

🌸 SYNOPSIS 🌸

When XPA can't allocate memory, it exits. You can arrange to have it call longjmp() instead. 💅

🦋 DESCRIPTION 🦋

So here's the tea, bestie. When an XPA server or client cannot allocate memory, it will attempt to output an error message and then exit. That's it. That's the whole vibe. Gone. Not coming back. 💀

If that is not satisfactory — like, say, maybe your program is interactive and can actually recover from OOM errors — you can tell XPA to call longjmp() to go to a recovery branch instead. main character energy fr fr. 👑

To pass the requisite jmp_buf variable to XPA, make the following call:

XPASaveJmp(void *env);

The value of env is the address of a jmp_buf variable that was previously passed to setjmp(). For example:

jmp_buf env;
...
if( setjmp(jmp_buf) != 0 ){
  /* out of memory -- take corrective action, if possible */
} else {
  /* save env for XPA */
  XPASaveJmp((void *)&jmp_buf);
}
// enter main loop ...

lowkey important: copy that example exactly as it is, bestie — yes, even the setjmp(jmp_buf) bit. we do not "fix" the manpage in this house. 🙈

🌈 SEE ALSO 🌈

See xpa(n) for a list of XPA help pages 💜

k bye bestie, go forth and handle your memory like a legend 🎀✨

this page is xpaoom(7) — version 2.1.15, July 23, 2013 🌸