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:

Hrmph. 1GB of RAM should be enough, and the W2k limit on threads is really very high, so there's no good reason you should be running out of space. All those clients may be using a large amount, but I kinda doubt they'd be using up so much space that you wouldn't be able to create a new thread. Does this error occur often? If so, does it happen if you close your other programs? The error could have an effect on download speed with LW, as right now (in the released versions) it uses a different thread for each source it's downloading from, so if it can't create the thread then it can't download from that source (and can't swarm and raise the speeds as high as it should).

Well, the crashes do not happen that often, let's say every two or tree days once or twice. Since yesterday I've suspended ond closed Boinc. I'm at the moment in a fierce discussion with my ISP, from which I get quite contrary statements in regard to them shaping my bandwidth ranging from denying to confirming, to not being sure if this is being implemented according to their contract rules (I spent 2 hours on the phone yesterday, ending up with not more than I knew before). I'm wondering, is there any way I could measure or test whether they really are shaping my bandwidth? I've made some screen shots from my task manager and from LW but I am not really sure what the information there hint at. Would you mind taking a look at them??;) :cool:

I've just made another screen shot of my Task manager about the networking.
Now I'm wondering, the peaks reach almost 100% for my adsl runner but the Network utilization is not more than 20%. Could that be the sign that my ISP shaping my bandwidth of about 80% ?????:eek: :eek: :confused: :eek: :eek:

Since my last post from yesterday I've done some things which I now wonder whether they are suitable for other LW users with similar problems?!?
Two days ago, when doing my 1st screen shot of the LW client, I had roughly 0-1kb/s with a "turbo charged' connection (like it was for the last couple of weeks).
And while reading yesterday some of the replies to speed problems and connection problems I used an advice of LOTR to change the listening port from 6346 to 64049 and make a manual port fowarding instead of UPnP.
Furthermore, I got interested in the 'Phex' client by chance and visited their website including their wiki. There I stumbled into tips for optimizing 'Phex' from someone namend Mike (may the Lord bless you:-)). Since I thought what might be good for this program can't hurt for LW, I became specifically interested in his first tip:

1. It appears that Microsoft (if you're using Windows XP this applies to you, otherwise skip to the next one) has decided to limit the number of consecutive connections to the internet to 10. For most users this is fine but when you have a P2P it can bottleneck things. http://trustyfiles.com/help-sw-xpsp2.php discusses this more in-depth and provides a link to a small utility file which will allow you to edit how many connections you have. I set mine at 100 since the max supported by Phex is 99.

Well, I followed the link and downloaded the small utility and used it.
The result of doing so, since yesterday I've been able to get (at least) 20-30KB/s, as you can see in the screen shot.
And now my question to the developer of LW. Do you think this increase of KB's is just incidentely lucky for my specific case, or do you believe that other users could also profit from using this nice small utility???;) :cool:

foolofthehill

The patch has been around for a while but it doesn't really make a difference until you get up into the 100s of KB/s. The thing that most likely mad a difference is the port forwarding to port 64049. When you did this and got more bandwidth it tells me that your ISP is most likely blocking or filtering the lower ports. Or your UPnP wasn't working correctly. Now if you want to find out if your ISP is blocking or filtering set your router to port forward to 6346 and limewire to port 6346. If your bandwidth drops down again you will know it is your ISP. If it doesn't then it was the configuration of you UPnP.