Comment 47 for bug 1608180

Some more ideas, from most to least probable:

1. We're dealing with some kind of stack corruption, e.g. because large object (or large number of objects) is allocated on stack, or local buffer gets overrun, destroying return address and we end up trying to resume execution from wrong memory.

2. Can you try to restart X11 server with VESA backend (slow) and see if it changes anything?

3. Faulty memory. You might try replacing RAM sticks (unless they're soldered) or run memtest86+ (e.g. from a live bootable CD as I recall FreeBSD port is broken on amd64).

qDebug() messages appear in the log when Stellarium is launched with -d or --verbose options.