nsappshell:eventwindow bug

nsAppShell is part of the mozilla "framework? (right word?)" Firefox/Thunderbird/Songbird/SunBird/... You should try contacting them and see if they can determine what might cause this. If it is wuala it should help us know why.

Kaspar, I'm using winxp latest updates I'm running firewall (outpost pro) and antivirus (avira)

I can't put into words how frustrating this bug is! If anything makes me dump wuala, this is it!

Just now I was using filezilla to ftp some files and in the middle of the trf it stopped dead. Then nothing worked. I have to restart and quickly disable/exit from wuala.

If wuala is not running, everything is fine. If wuala is running, this bug rears its head and stops internet traffic.

Please take this seriously. I use waula and love what you guys have created but this is simply too much.

Since everything plays nice on the system and things go haywire once wuala comes online and starts uploading/downloading, this is wuala's problem.

Please try wuala using the compatibility mode in the setting. You will not be able to share anymore - wuala is just using tcp to the servers and no p2p in that mode - but we can see if this error belongs to the p2p part. If it is, its a good chance that kaspars first idea that the network traffic using p2p creates the problems.. Maybe we can go on then..

actually, I'm using wuala for backup by trading storage space so turning that off would remove my reason for using wuala in the first place!

This should not be for ever. Just to see if it is the p2p-action or not. ;) Ok - let us think.
You ́re using wuala for a longer time now without problems. The problem has appeared a short time ago? If it is - what has changed at the time the problem appears?

You are this time the only user who is descriping this problem. So Wuala conflicts with something very unique on your system. Maybe we can find out what it is..

I see your point. ok I'll give it a try. to be honest, this problem has been an issue from the very beginning but it is really grating on me now

So when it is from the very beginning, we can get no hint from changes on the system..

I ́ll try to find two older threads I remember but im not able to find them yet. hmm.

They has descriped also problems with craching internet connection. I one thread, the problem was created from the router who was not able to open a lot of connection, wich is neccesary for wuala. If your connection is stable with the "compatibility mode", theres a good chance that this is the problem. If it is, and you have somenone with an other router wich you can lend for a test, this will be an idea.
This time, there is no way to limit the number of connections in wuala. Afaik this will be supported in the future, but there is no deadline yet when this option should be implemented.

The second has depended on a upnp-problem. There are some other (p2p-) programms who are using the same port than wuala to manage the upnp-settings with the router. I ́ll do not remember if the connections have crashed on that point or wuala e.g. the other program was "only" not connecting anymore. Maybe you can config a fix Nat for wuala in your router setting so that upnp is not used, to be on the safe side here..

Hi. I have this problem too, but it only occurs when running Second Life. I don't know what Wuala is, and had never heard of it before stumbling across this page via google.

I get the same symptoms. "broken" internet connection, only fixed with a restart. and the same nsAppShell error on shutdown. I think Mozilla firefox is the common cause here

Do you have many add-ons in firefox?

I have quite a few

4chan
Adblock Plus
Adblock Element hiding helper
Cookie Culler
Download Helper
Greasemonkey
IE tab
iMacros for Firefox
Linkification
NoScript

It would be nice to get a list of what babak has, see if any correlate.

I don't think this is simply a Firefox bug because it effects internet traffic with other browsers as well - when it happens, I can't even use opera or IE etc. As well, when wuala is disabled, it doesn't happen. It only comes up when wuala is running. And no, it isn't a router issue either.

And to report back from the experiment that bagelcat suggested, I've been running wuala with p2p disabled and it is the same issue. The only other nugget I can suggest is when I sign in to wuala it happens more often but that's just a hunch, not really proven to me yet, it just seems that way.

It may not "Simply" be a firefox bug. But it does not seem to be "Just" Wuala. The question is what is the common denominator. Second Life and Wuala both use UDP.

Also, when the internet locks up:
1. If on vista, go to Resouce Monitor and see if anything is using alot of netowork.
2. Try killing firefox.exe and closing ALL applications and see whats left in the process list and if the internet works (and if you can access the router/modem).
3. Try disabling and re-enabling the network adapter.

It looks like this is a firefox weakness which when combined with certain other software makes the computer or firefox freak the frak out.

Some are reporting this in concurrance with AVG and others (like myself) with Outpost. The only thing which is constant is that both of those "monitor" info to and fro from the browser - sorry that's about as technical as this noob gets.

https://support.mozilla.com/tiki-view...

So it seems that wuala can also be one of these pieces of software because it also sends and receives traffic. But strangely enough, I could swear that at times utorrent isn't restricted and at other times it is. Is there something inherently different between utorrent and firefox or secondlife? maybe UDP??!?

In any case, I can definitely say that it isn't an add on issue as many people suggest. I've disabled them and it still occurs. It is something in the Gecko engine which collides with AVG or Outpost or wuala or etc.

I say this with confidence because I've done the SAME action in opera with no problem (uploading a file) but with firefox, everything else being equal, it pukes nsappeventshell:window.

My hearty apologies for sullying the good name of wuala :-/ it was misplaced frustration. Try to imagine having to restart your station 45 times in a day.

I have had the exact same problem you describe, with the nsappshell message. However, I don't think I use waula (I don't even know what it is), but I do have mozilla firefox on my computer. Did you ever find a solution?

It's one of those errors that doesn't make any sense.