Possible memory leak 0.3.5.2
 

News:

29 December 2022 - PtokaX 0.5.3.0 (20th anniversary edition) released...
11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

Possible memory leak 0.3.5.2

Started by CrazyGuy, 18 January, 2007, 22:44:11

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

CrazyGuy

Uptime compared with memory usage

Quote

------------------------------------------------------------
Current stats:
------------------------------------------------------------
Version: PtokaX DC Hub 0.3.5.2 built on Nov  1 2006 11:01:55
Uptime: 0 days, 0 hours, 14 minutes
Users (Max/Actual Peak (Max Peak)/Logged): 500 / 156 (202) / 155
Users shared size: 16986636722648 Bytes / 15.45 TB
.
.
.
------------------------------------------------------------
CPU usage (60 sec avg): 1.67%
CPU time: 0:00:50
Mem usage (Peak): 7.89 MB (11.52 MB)
VM size (Peak): 9.25 MB (9.57 MB)
------------------------------------------------------------
.
.


Quote
------------------------------------------------------------
Current stats:
------------------------------------------------------------
Version: PtokaX DC Hub 0.3.5.2 built on Nov  1 2006 11:01:55
Uptime: 12 days, 23 hours, 37 minutes
Users (Max/Actual Peak (Max Peak)/Logged): 500 / 177 (202) / 164
Users shared size: 18827719987007 Bytes / 17.12 TB
.
.
.
------------------------------------------------------------
CPU usage (60 sec avg): 2.70%
CPU time: 8:22:25
Mem usage (Peak): 83.16 MB (183.85 MB)
VM size (Peak): 104.11 MB (190.34 MB)
------------------------------------------------------------
.
.



As the devlog shows some memory fixes already for the 0.3.5.2d debug version, this might be fixed.
For PPK to confirm :)



Tw?sT?d-d?v

Seems ok here m8



------------------------------------------------------------
Current stats:
------------------------------------------------------------
Version: PtokaX DC Hub 0.3.5.2d built on Jan  7 2007 19:50:30
Uptime: 5 days, 23 hours, 54 minutes
Users (Max/Actual Peak (Max Peak)/Logged): 300 / 102 (308) / 96
Users shared size: 109988127785363 Bytes / 100.03 TB
Chat messages: 153 x
Unknown commands: 43803 x
PM commands: 277 x
Key commands: 4279 x
Supports commands: 4551 x
MyINFO commands: 32080 x
ValidateNick commands: 3533 x
GetINFO commands: 0 x
Password commands: 2199 x
Version commands: 1957 x
GetNickList commands: 2240 x
Search commands: 138092 x (0 x)
SR commands: 11242 x
CTM commands: 743717 x (0 x)
RevCTM commands: 150417 x
BotINFO commands: 49 x
Close commands: 0 x
------------------------------------------------------------
CPU usage (60 sec avg): 0.00%
CPU time: 0:15:07
Mem usage (Peak): 22.65 MB (26.81 MB)
VM size (Peak): 40.20 MB (40.88 MB)
------------------------------------------------------------

PPK

Maybe is leak, but more it looks like i have somewhere problem with signed/unsigned int and they cause bad memory allocation of send buffers  ::)
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

CrazyGuy

Quote from: PPK on 19 January, 2007, 18:50:42
Maybe is leak, but more it looks like i have somewhere problem with signed/unsigned int and they cause bad memory allocation of send buffers  ::)

Aren't those pointed out as warnings when compiling ? ::)  :P

PPK

Only when comparing signed/unsigned ... i need to check better compiler warnings setting.
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

SMF spam blocked by CleanTalk