On 10/25/05, Ian McDonald <[EMAIL PROTECTED]> wrote: > I just tried replicating this but it didn't do the same for me. It did > run slow due to constant resyncing like you were having also. This is > a problem that we are aware of but shouldn't cause the crash. > > I don't claim to understand what the memory parts are saying but I > suspect you have fast machines with fast ethernet cards and it is > running the machine out of memory. Can somebody else confirm that the > machine is actually running out of memory? > > If this is the case then I think we need to put some limits on DCCP > buffers much like TCP does.
Yes, this is something I haven't worked on the CCID3 code, all the packet history allocations _have_ to be accounted to the sock, definetely needs to be fixed. Bruce, please try disabling the ccid3_debug variable, the CCID3 code is spamming syslog in your case with way too many messages, without it your program perhaps can make some more progress and get us more info out of just the core dccp debug messages. - Arnaldo - To unsubscribe from this list: send the line "unsubscribe dccp" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
