On 05/12/06, <b class="gmail_sendername">Klaasjan Brand</b> <<a href="mailto:klaasjan@gmail.com">klaasjan@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<span class="q"></span><div><div><br>Maybe related to "my" crash bug: <a href="https://maemo.org/bugzilla/show_bug.cgi?id=820" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">https://maemo.org/bugzilla/show_bug.cgi?id=820
<img class="targetalert" style="border: 0px none ! important; margin: 0px 0px -3px 5px ! important; padding: 0px ! important; display: inline ! important; background-color: transparent ! important; width: auto ! important; height: auto ! important; float: none ! important; z-index: 10 ! important;" src="chrome://targetalert/content/skin/new.png">
</a></div></div></blockquote><div><br>probably similar or the same, it wasn't just xterm, also another big package I installed<br>I'm using WPA on a 54Mbit/s linksys/openwrt AP/router<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><span class="q"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
If I understand the few comments I've seen on this, there's a watchdog program running and it kills the device when it's using too much CPU in one go (not releasing the CPU to the kernel so it can ping the watchdog). I'm tempted to report a bug on the application manager for this, but I just want to make sure this is really the correct interpretation.
</blockquote></span><div><br>Do you only notice the problem within the application manager? I've seen it also when browsing for some time.</div></div></blockquote><div><br>Also opera, I think it must be related to how the file transfer function is implemented in these applications, not releasing the CPU could cause it to crash on big files (taking a certain time at high CPU load)
<br></div><br></div>Cheers<br><br>Simon<br>