Opened 4 years ago

Last modified 4 years ago

#4280 reopened defect

memory leaks after refreshing users db

Reported by: schamen Owned by:
Priority: major Component: General
Severity: high Keywords: memleaks webif usersdb refresh
Cc: Sensitive: yes

Description

Revision

10937

memory leaks after refreshing users db

When the issue occurs

when reload users db (kill -1 or refreshing in webif)

How the issue is reproducable

reload users db

Attachments (1)

valgrind.rar (5.9 KB) - added by schamen 4 years ago.
Valgrind log

Download all attachments as: .zip

Change History (6)

Changed 4 years ago by schamen

Attachment: valgrind.rar added

Valgrind log

comment:1 Changed 4 years ago by schamen

it's some clarification, oscam eating mem when refreshing clients db 10-15 times per second. i mind kill -1 pidofoscam

comment:2 Changed 4 years ago by Aeon

Resolution: invalid
Status: newclosed

The only real leak in the log is
576 bytes in 1 blocks are definitely lost in loss record 43 of 69
and it is related to the reader-db, not the user-db.

Last edited 4 years ago by Aeon (previous) (diff)

comment:3 Changed 4 years ago by tommys

Resolution: invalid
Status: closedreopened

so can we fix the reader DB memory leak? my oscam sometimes is taking over 3gb of memory over time... and needs to be killed and restarted.

comment:4 Changed 4 years ago by Aeon

the leak I was talking about will only happen if you modify readers a lot, and will never be bigger than a few bytes.

if your oscam is going over than 3 GB then, this must be another problem/leak.
you should create a valngrind log AFTER oscam used ~500 mb ram in this case

comment:5 Changed 4 years ago by schamen

@Aeon maybe so, but then tested with about ~700-900 users accs in 10 days oscam eat 1.3% of mem and it still eating 0.3% each 3-4 days (user db refreshed in 1 hour), but other copy still used .2% after 16 days and this copy don't use db refreshing.
Function called after sighup edited and it's only user db refresh func inside and where is no other modification made.
Thanks for attention

compiled options:

SSL support: no
DVB API support: no
Monitor: no
LCD support: no
LED support: no
Clockfix with realtime clock: no
IPv6 support: no
camd 3.3x: no
and cardreaders is off

Note: See TracTickets for help on using tickets.