I tested if current master 677ef4b is ready for year 2038 problem, and it seems there are some issues:
Testing this inside a VM with Debian 13.4.
Very simple test, set a date after year 2038 problem and launch amule:
- sudo timedatectl set-ntp false
- sudo timedatectl set-time "2040-01-01 01:01:01"
- launch amule, it immediately goes to 100% CPU and memory spikes
The log I could get before killing it:
2040-01-01 01:03:33: Initialising aMule GIT compiled with wxGTK3 v3.2.8 and Boost 1.83 (Snapshot: rev. 2.3.3-377-g677ef4b95)
2040-01-01 01:03:33: Checking if there is an instance already running...
2040-01-01 01:03:33: No other instances are running.
2040-01-01 01:03:33: ListenSocket: Ok.
2040-01-01 01:03:33: Loading temp files from /home/user/.aMule/Temp.
2040-01-01 01:03:33: All PartFiles Loaded.
2040-01-01 01:03:33: Asio thread 1 started
2040-01-01 01:03:33: Asio thread 2 started
2040-01-01 01:03:33: Asio thread 3 started
2040-01-01 01:03:33: Asio thread 4 started
We still have 12 years to fix it, but if we do a release every five years, we are just a couple of releases away :D
I tested if current master 677ef4b is ready for year 2038 problem, and it seems there are some issues:
Testing this inside a VM with Debian 13.4.
Very simple test, set a date after year 2038 problem and launch amule:
The log I could get before killing it:
We still have 12 years to fix it, but if we do a release every five years, we are just a couple of releases away :D