You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
aMuleD 2.3.3 compiled with wxBase(GTK2) v3.0.5 and Boost 1.74
Debian Bullseye
I run a 24/7 server and sometimes the amuleweb process crash without a reason. Amule GUI is still working after amuleweb crash.
The only information I can find is these traces:
2021-04-12 07:32:35: External connection closed.
2021-04-12 07:32:35: Command ''amuleweb' '--amule-config-file=/home/amule/.aMule/amule.conf'' with pid '40' has finished with status code '-6'.
UPDATE:
I crashed again but this time I got the traces. The crash was after clicking in the stats tab in the web ui.
--------------------------------------------------------------------------------
A fatal error has occurred and amuleweb has crashed.
Please assist us in fixing this problem by posting the backtrace below in our
'aMule Crashes' forum and include as much information as possible regarding the
circumstances of this crash. The forum is located here:
http://forum.amule.org/index.php?board=67.0
If possible, please try to generate a real backtrace of this crash:
http://wiki.amule.org/wiki/Backtraces
----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: amuleweb 2.3.3 compiled with wxBase(GTK2) v3.0.5 and Boost 1.74
Running on: Linux 5.10.17-v7l+ armv7l
[2] ?? in amuleweb[0x452504]
[3] ?? in /usr/lib/arm-linux-gnueabihf/libwx_baseu-3.0.so.0[0xb6ee2748]
[4] ?? in /lib/arm-linux-gnueabihf/libc.so.6[0xb6a04cb0
UPDATE2:
I can reproduce the issue all the times in my machine. I have been running amuled from 5 days so maybe it's related to having too much data in memory or something like that.
the C++ code that renders that image (with loaded data) crash the whole program.
UPDATE3
Ok, after more research I think the issue is because the value in amule_stats_kad.png image keeps increasing over the time. The first days the image / webui is ok but after 4 or 5 days the numbers are high (more than 10.000) and the code that generates the image crash (maybe the integer types are not enough).
@gonosztopi I'm very sure about this issue and the cause. I hope you can fix it soon.
The text was updated successfully, but these errors were encountered:
aMuleD 2.3.3 compiled with wxBase(GTK2) v3.0.5 and Boost 1.74
Debian Bullseye
I run a 24/7 server and sometimes the amuleweb process crash without a reason. Amule GUI is still working after amuleweb crash.
The only information I can find is these traces:
As a workaround I can do one of those things:
amuled
processamuleweb --amule-config-file=/home/amule/.aMule/amule.conf
manuallyIs there a way to enable
amuleweb
logs / debug?UPDATE:
I crashed again but this time I got the traces. The crash was after clicking in the stats tab in the web ui.
UPDATE2:
I can reproduce the issue all the times in my machine. I have been running amuled from 5 days so maybe it's related to having too much data in memory or something like that.
Steps to reproduce:
That page
amule/src/webserver/default/amuleweb-main-kad.php
Line 11 in d105aa2
UPDATE3
Ok, after more research I think the issue is because the value in
amule_stats_kad.png
image keeps increasing over the time. The first days the image / webui is ok but after 4 or 5 days the numbers are high (more than 10.000) and the code that generates the image crash (maybe the integer types are not enough).@gonosztopi I'm very sure about this issue and the cause. I hope you can fix it soon.
The text was updated successfully, but these errors were encountered: