LimeWire 4.11.0 Internal error
 

Twice in the last few days while running LimeWire has had a pop-up come up and say LimeWire has encountered an internal error and may be able to recover do you want to send a report. I have ticked yes and sent the report.

Today I was running as a UP DL nothing sharing 3 LimeWire 4.8.1 dmg for those MAC users having problems. 9 files needing more sources. What ever the problem was it did not appear to affect LimeWire It kept all connections and every thing appears to be normal. Same as last time I received the pop-up
the only difference the last time I was not running as a UP last time. And I was running in UPnP mode last time and Forwarding this Time.

Any way below are a couple of stack traces I took a couple of minutes after I received the pop-up.

I tried to copy and paste it but I could not. How can I save it. It happened a couple of more times yesterday so I am sure it will happen again.

ctrl-a & ctrl-c should work.

Thanks

sberlin

It did it again over night.

Internal error
 

Before going on vacation I had 2 LW crashes of which I could save one error message. While consulting about some other problem at a different thread ( http://www.gnutellaforums.com/showth...=27036&page=14 ) I was adviced to post here to ask for some input.

My errror message was/is: http://www.gnutellaforums.com/attach...9&d=1144607534

I also experience some crashes with Fire Fox browser, sometimes when posting at forums and lately after the virus attachment scan from hotmail when forwarding mails. I'm not sure whether both things are connected in any way. However, I would appreciate if someone could look into the error message and give me some advice. If any further datas will be necessary, let me know and I'll try to get them with the little amount of computer knowledge I have...:o :o ;) :o :o

I was able to reproduce the FF crash and saved that bug report as well, if it is of any help for the one who might be able to look at it. :cool:

Yeah, the reason both problems are happening may be the same. What that reason is, I don't know. LimeWire's reporting that it's unable to create a new thread, and FireFox may also be running into the same problem (but handling it less gracefully). Fortunately (for LimeWire, atleast) we've spent the past month+ working on reducing the number of extra threads needed for the program to run. The next beta should be using a single thread for all connections, downloads, maybe uploads, and a host of other things.

Which means I've to live with it for now and wait until the next beta is released ?!
Thanks for your input pal
Cheers
Mario;) :cool:

Well, sorta. You could try and figure out what's preventing your machine from letting a new thread be created. It might be a shortage of RAM, or there's another program running that is using up a lot of memory. I'm not really an expert on Windows internals, so I don't really know what to look for in causing the problem. It is a pretty bad problem though and can have all kinds of weird/ugly consequences in various programs.

Hmm, thanks for this statement. Lets me think whether my BOINC client crushing SETI, Einstein, LHC and climate@home datas on "always run" may have that specific impact. Because I actually thought with 1.024GB Ram I should be on the save side. Upgrading to 2GB Ram might be a solution (or more, if that would be technically possible). Do you think that this also might have an effect on my download speed with LW? Maybe that LW runs out of ram source when sending data portions forth and back??:confused: