search for: memoryleaks

I noticed that tinc is using quite a big amount of memory after some time. PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ Command 11559 root 9 0 129m 73m 1092 S 0.0 39.1 0:22.06 tincd you can see that after 22 hours the memsize is way too big. im using debian sid. kernel 2.4.20. tinc 1.0pre8 debian package. greetings christian Tinc: Discussion list

Thanks a lot for answering. Before I get into it, please note that everything below bears the big capture "Thanks for trying to help me at all". 1) Yeah, those examples - quite hard to satisfy everyone's needs ;-) While the one side complained that my past examples regarding this issue were not informative enough, others didn't like the more elaborated version (as seems to be

Howdy, I am a C and C++ programmer -- how can I start helping with some basic coding for wine? Thanks, Will

Sorry guys, didn't see your responses before sending mine. Thanks jeroen!! I'll test your version today and get back to you. Gesendet von meinem Smartphone Am 15.12.2014 12:12 schrieb "Janko Thyson" <janko.thyson at gmail.com>: > Thanks a lot for answering. Before I get into it, please note that > everything below bears the big capture "Thanks for trying to

I currently have 2 x ESXi boxes that have VMs stored on a NFS/iSCSI debian lenny linux box. I had purchased a new whitebox server as an intended replacement for the linux box. I had always planned on installing opensolaris on the new hardware with this config; 2 x 640GB mirrored rpool 6 x 1TB in raidz2 This box was going to be built in parallel with the current server and I would have simply

https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=68 ------- Additional Comments From laforge@netfilter.org 2003-03-20 10:55 ------- This looks strange. The BUG in slab.c tells us that there is a GFP_ATOMIC missing. This means that we are allocating kernel memory from softirq context with only GFP_KERNEL. If I understand your backtrace correctly, what happens is: - you are

Dear list, I'm sorry to keep coming back with this time and time again, but this bug is still not fixed even though the root cause of the issue has been around for 2-3 years now. And as the number of packages that depend on XML grows, I thought maybe this deserves some wider attention. I did my best to make reproduction of the issue as easy as possible: