Hyperion keeps crashing with segmentation fault

[therazorgirl]

Hi

I'm running ubuntu 18.04 under latest git pull of Hyperion and it keeps crashing randomly, especially when I'm compiling. I tried to compile openssl 1.1.1g and well into the compilation this happens:

    +++ OOPS! +++

Hercules has crashed! (Segmentation fault)

Crash dump NOT created due to ulimit setting...

I've tried various memory configurations and it seems the more memory I add the sooner Hyperion crashes. It seems most stable with 4096 mb but still crashes.

Is this a known problem or am I missing something in my hercules.cnf?

[agadsby]

Check your Linux memory and swap space: `free -h`. I suspect you have run out of Linux memory. You probably have an out of memory process killed warning in your Linux logs. Try add more Linux swap. Andy

[therazorgirl]

Hi Andrew

Thank you for the reply. Indeed the swap was far too small, so I increased it and gave the Linux vm 12 Gb of memory, booted and tried to compile. The compilation went on for some time and then Hercules segfaulted.

The last recorded memory usage was 125 mb of ram and 0k in swap, so does not seem to be memory related. I rebooted the vm and then Hercules segfaulted again without any activity on the Linux vm. I have tried to recompile Hyperion with POSIX threads and do the OpenSSL compilation, but it doesn't change anything; Hercules still segfaults.

Maybe its unrelated, but I had lots of problems installing Ubuntu on Hyperion. It kept segfaulting during install until I gave the profile 1024 mb and then it installed (it segfaulted on 4096 mb and 2048 mb).

Right now while I'm writing this, Hercules segfaulted again without any activity on the Linux vm. It seems the more memory I give it the more unstable it becomes.

[agadsby]

OK, so what are you running Hercules on? OS and hardware size. Andy

[Fish-Git]

General FYI regarding email replies:

I would very much appreciate it if you would not respond/reply to GitHub Issues via email.

I would much prefer that you instead respond/reply directly via the GitHub Issues web page itself:

• https://github.com/SDL-Hercules-390/hyperion/issues/XXX

When you reply directly via their web page, I can make minor edits to your reply so it is more readable (prettier) by editing the fonts being used, formatting of log messages, etc.

When you reply via email however, I cannot edit your reply (GitHub does not allow editing of emails), so oftentimes it is much harder (more difficult) to read.

GitHub also does not allow attachments in their email replies either, making it impossible to receive a file that may have been requested from you.

It is up to you whether or not you want to take the time to reply via their web page or continue to reply via email, but it is generally preferable that you reply directly via their web page instead. Especially if you need to attach a file that was requested from you.

Thanks for understanding.

[Fish-Git]

More information needed:

• SUBMITTING PROBLEM REPORTS #373

[therazorgirl]

Hercules is running under Ubuntu 22.04 in a VBox with 16 GB of RAM and a 50 GB vda. The host is a win 11. Hercules was compiled with the standard Ubuntu tool chain. I have successfully run different types of Hercules installations in a VBox through the years.

I tried with a 2048 mb profile and different workload and the same happened, approx 100 min after workload is started, Hercules segfaults and the about 105 mb of ram are utilized and 0k of swap. I've done a time trace on the VBox guest and prior to Hercules announcing it has segfaulted, the ticker freezes and there are timestamp gaps, so the whole guest freezes at the same time, and after the segfault the guest becomes unusable and needs to be restarted.

I'll try other versions of Hercules and see if they work, so closing ticket.

[agadsby]

I know this has been closed, but how much physical memory is on the physical Windows box?

[therazorgirl]

Hi Andrew

I feel very uncomfortable with sharing any additional information as Mr. Fish is watching. If you want you can contact me on r a z o r g i r l AT n i g h t c i t y dot j p and I can can supply you with lots more details and results of additional tests I've been making.

[Fish-Git]

I feel very uncomfortable with sharing any additional information as Mr. Fish is watching.

?!

Why do you feel uncomfortable with me? What have I done to make you feel uncomfortable? I'm simply trying to HELP you!

In order to be able to help you, it is important to provide specific information about the problem you are having, as explained in "SUBMITTING PROBLEM REPORTS" link that I provided earlier.

Enabling Crash dumps (core files) on your system and then analyzing them when they are created (i.e. obtaining a backtrace) is also important, as explained in "How to analyze a Linux "core" file (i.e. crash dump)".

As our "SUBMITTING PROBLEM REPORTS" document explains, we are not psychic! If you want our help, you need to provide enough helpful information as possible so that we are able to help you!

Why does respectfully requesting such information make you feel uncomfortable? I don't understand! Do you want our help or not?   <me: confused!>