System Information
| Field | Value |
|---|---|
| Operating System | Linux - Debian GNU/Linux 13 on x86_64 |
| Product | AMP ‘Phobos’ v2.6.5.0 (Mainline) |
| Virtualization | VMware |
| Application | Application Deployment |
| Module | ADSModule |
| Running in Container | No |
| Current State | Indeterminate |
Task
AMP Service Hangs and Crashes
Problem Description
Issue
We are continuing to experience repeated hangs and crashes of the AMP Discord service, despite the system operating well within normal resource limits. This issue has been ongoing for an extended period and is reproducible during normal operation.
While actively working inside AMP, the panel becomes unresponsive. Shortly afterward, AMP either crashes outright or the Discord service restarts without warning. This occurs without any corresponding spike in CPU, memory, or system load.
A screenshot has been attached showing the system state at the time of the issue:
Observed system state at time of failure (per htop):
Total RAM: ~9.7 GB
RAM in use: ~446–500 MB
CPU usage: ~0.7% per core
Load average: 0.12 / 0.31 / 0.25
No memory pressure
No CPU saturation
No abnormal process growth
AMP-related processes are present and stable at the OS level, with multiple AMP Core processes running at approximately 290 MB RES each, but overall memory usage remains extremely low relative to available system resources.
Despite this healthy system state, AMP becomes unresponsive and crashes, which strongly suggests:
An internal AMP Discord integration issue
A deadlock or thread stall
An unhandled exception within AMP
A watchdog or supervisor incorrectly triggering restarts
A logic or state failure unrelated to resource exhaustion
There is no indication that this behavior is caused by the host, Docker, containerd, or systemd. The host remains fully responsive during the incident.
This is not a one-off event. It happens during normal usage patterns and interrupts active management work. Manual recovery is often required.
We need assistance identifying what is causing AMP to hang and crash when the system is demonstrably healthy.
Requesting assistance with:
Root cause analysis of AMP Discord service hangs/crashes
What logs or debug flags should be enabled to capture the failure
Whether this is a known issue with the AMP Discord module
Any patches, updates, or configuration changes that address this behavior
How to prevent AMP from crashing under low-load conditions
This issue is impacting reliability and needs to be addressed beyond basic resource troubleshooting.
Reproduction Steps
- Login in to amp
- Start working on server
- AMP stops working
- Amp Service Hangs
- Amp Crashes