What does this error in llink mean?

[litfoo]

connections_new: buffer area malloc: not enough space

am using llink for windows 2.3.2

many thanks

litfoo

[lundman]

Wow, hmm, that's a new one. Ok the code has

Code:

// Allocate input buffer
  result->buffer = (char *) malloc(buffer_size);

  if (!result->buffer) {

    perror("connections_new: buffer area malloc:");
    exit(1);       // FIXME.

  }

Which means it wanted to allocate a new buffer for the connection, and the size used is default 1400, or whatever value you set in

HTTP|BUFFERSIZE=

If you have set a very large number, it will probably fail everytime. If it fails after some long-time usage, maybe there is a leak somewhere and you run out of memory.

[litfoo]

(01-21-2012 02:20 AM)lundman Wrote:  Wow, hmm, that's a new one. Ok the code has

Code:

// Allocate input buffer
  result->buffer = (char *) malloc(buffer_size);

  if (!result->buffer) {

    perror("connections_new: buffer area malloc:");
    exit(1);       // FIXME.

  }

Which means it wanted to allocate a new buffer for the connection, and the size used is default 1400, or whatever value you set in

HTTP|BUFFERSIZE=

If you have set a very large number, it will probably fail everytime. If it fails after some long-time usage, maybe there is a leak somewhere and you run out of memory.

thanks for this lundman. i have not edited the buffer size from the default so have restarted it and will monitor to see if it happens again

it failed last time after 1 day of usage so let's see

[litfoo]

Sad to say that it has happened again with the same message.

what can I do to remove these errors?

was really counting on llink to be the answer to my network mount problems, but at the moment I am fearing the worse with these errors.

cheers

[lundman]

Changed the print on error to show the attempted allocation size, please try this binary

http://lundman.net/ftp/llink/llink.exe

[litfoo]

(01-25-2012 01:29 AM)lundman Wrote:  Changed the print on error to show the attempted allocation size, please try this binary

http://lundman.net/ftp/llink/llink.exe

Thanks for this lundman.

I just have to rename my old llink.exe to say llink_original.exe and replace with your new llink.exe ?

[lundman]

Yeah, you can rename it if you want, or overwrite. (You can always download the original again too, but renaming is painless.) You can also call the new one "llink_test.exe" and run that instead.

[litfoo]

Thanks for the suggestions lundman.

Am trying at the moment and looking ok for the moment.

So this version, R2569 - it will output more detail for debugging should I get the error again?

you also mentioned I could re-download the original from your website - what revision will this be?

any way to tell without downloading first?

[lundman]

I have no idea, I dont pay attention to build numbers at the moment

[litfoo]

haha.

just wanted to understand - the purpose of the new binary will be to output more detail for debugging should I get the error again? and not an actual fix?

[lundman]

it will print some more things yes, like buffer size attempted to allocate

[litfoo]

OK - I tried the binary you gave me and I get this message continously:

PICKING NO LOCK FOR gfb107

[lundman]

yeah we are hunting two bugs at the same time, ignore that one.

[litfoo]

Ok - should this message appear just once?

I recall it continuously appearing in the console window.

[lala]

Maybe the IRPStackSize in registry is set too low? Could be the reason for "memory problems"