unraid onedrive container memory error

[abraunegg]

@addohm
Taken from: https://forums.unraid.net/topic/156184-out-of-memory-errors/#comment-1381059

• Segmentation Fault (segfault) at 0: A segmentation fault occurs when a program attempts to access a memory location that it's not allowed to access. The at 0 part indicates that the process tried to access the memory address 0, which is typically not accessible to user-space programs. This can happen for various reasons, including dereferencing a NULL pointer.
• Instruction Pointer (ip) 0000000000000000: The ip (Instruction Pointer) indicates the memory address of the next instruction the process will execute. An address of 0 suggests the program attempted to execute code at a null address, possibly due to a null function pointer call.
• Stack Pointer (sp) 00007ffc84ff32a8: The sp (Stack Pointer) points to the current location in the process's stack. This is where the process was operating in memory at the time of the fault.
• Error 14: This part of the message specifies the type of error that caused the segfault. Error 14 typically indicates a page fault occurred because the process attempted to access a memory page that was not present.
• CPU and Core Information: The error indicates that the fault was "likely on CPU 2 (core 2, socket 0)," providing information on which CPU and core the error was most likely to have occurred on.

Potential Insights and Fixes

1. Null Pointer Dereference: The most common cause of attempting to access memory address 0 is dereferencing a null pointer.

2. External Libraries or Dependencies: If the onedrive process relies on external libraries, ensure they are up-to-date and compatible. An incompatible or buggy library can lead to segmentation faults.

3. Hardware Issues: Although less likely, persistent segmentation faults, especially if occurring randomly across different programs, could hint at underlying hardware problems, such as faulty RAM or CPU issues. Running hardware diagnostics might help identify or rule out this possibility.

4. Debugging Tools: Use debugging tools like gdb (GNU Debugger) to run the onedrive process and analyze its execution flow. This can help identify exactly where and why the segmentation fault occurs.

5. System Logs and Core Dumps: Check system logs for any related messages that might offer more context. If core dumps are enabled, the dump generated by this segfault could provide valuable insight into the program's state at the time of the crash.

Given the nature of the fault, I am unsure if you got this error with v2.4.25 or if you have been testing a version of v2.5.0 in your container.

In either case, given that RC-1 is now available, to build a docker container of v2.5.0 RC1:

git clone https://github.com/abraunegg/onedrive.git
cd onedrive
git fetch origin pull/2661/head:pr2661
git checkout pr2661

then, from inside the 'onedrive' clone that is pointing at RC1:

docker build . -t local-ondrive-debian -f contrib/docker/Dockerfile-debian

This will ensure that your container is built against Debian 12, pulling in all the latest versions of aspects for Debian, and you will be using v2.5.0 RC-1 codebase.

If this problem persists with v2.5.0 RC-1:

1. Enable debug logging for your container, ensure that a log file is being written out
2. Capture all Docker logs when the issue is occurring
3. Open a new bug and provide all the debug logs & Docker logs of the error