The Following 17 Users Say Thank You to felbutss For This Useful Post: | ||
|
2010-06-16
, 13:38
|
|
Posts: 2,121 |
Thanked: 1,540 times |
Joined on Mar 2008
@ Oxford, UK
|
#2
|
|
2010-06-16
, 16:28
|
|
Posts: 579 |
Thanked: 286 times |
Joined on Oct 2009
@ Australia
|
#3
|
|
2010-06-16
, 19:40
|
Posts: 296 |
Thanked: 10 times |
Joined on May 2010
|
#4
|
|
2010-06-17
, 04:11
|
|
Posts: 579 |
Thanked: 286 times |
Joined on Oct 2009
@ Australia
|
#5
|
The Following User Says Thank You to felbutss For This Useful Post: | ||
|
2010-06-17
, 04:54
|
Posts: 726 |
Thanked: 345 times |
Joined on Apr 2010
@ Sweden
|
#6
|
like i said before. dont ever expect this issue to be fixed. their stance on this issue is its 'our fault'
|
2010-06-17
, 06:51
|
|
Posts: 579 |
Thanked: 286 times |
Joined on Oct 2009
@ Australia
|
#7
|
Each widget is actually a separate process, which runs its own interpreter instance.
With the new Opera Widgets for Desktop we managed to break the dependency between widgets and the browser interface. From now on you don't have to have the Opera Browser open to run a widget. Furthermore, each widget runs in a separate process and integrates with the platform much better
New Opera Widgets for Desktop
A new platform allows Opera Widgets to move beyond the Web browser and onto your desktop. Multi-process architecture allows each widget to run as a separate process. Native OS integration now lets widgets behave like normal applications.
Opera is designed to restart and recover all your tabs if a crash occurs
Stability and resource-utilization improvements Put each document into an independent process (not thread: separate forked process) so that:
- When a document causes Firefox to crash, the whole browser won't be taken with it.
- When a bug in Firefox stomps on memory it doesn't own, other documents in memory are not corrupted.
- When a document causes Firefox to leak massive amounts of memory, closing that tab or window will free up the wasted memory.
- Memory fragmentation: If I open three documents, then close the second one, no memory is returned to the OS for other apps, because memory is only freed to the OS from the end of the heap. Also, however, I notice that if I open one document (and check the memory size), then open two more, then close the last two, the process size does not shrink back to what it was with only the first document (this looks like a memory leak). Putting each document into its own address space would solve these problems, because processes that terminate free all of their memory to the OS.
- When a bug in Firefox or a script on the page locks up (infinite loop or whatnot), the whole browser will not hang up
|
2010-06-17
, 07:39
|
|
Posts: 186 |
Thanked: 192 times |
Joined on Jan 2010
@ Finland
|
#8
|
Regarding your suggestion, I think it might be a little too costly to have separate processes, as in one per widget.
|
2010-06-17
, 08:46
|
|
Posts: 2,121 |
Thanked: 1,540 times |
Joined on Mar 2008
@ Oxford, UK
|
#9
|
The Following User Says Thank You to pelago For This Useful Post: | ||
|
2010-06-17
, 09:01
|
|
Posts: 1,079 |
Thanked: 1,019 times |
Joined on Mar 2010
|
#10
|
_______________Symptoms_______________
*You Media player widget play button stop working
*you lost all of your widgets for no reason
*you have high CPU usage
*your home screen is unresponsive
*your N900 comes slow and jerky after a few days
*your N900 battery starts to drain fast until you restart
________________________________________
_______________Problem_______________
* PR1.2 was seriously delayed for many reasons but one of those reasons which is still not fixed is this bug https://bugs.maemo.org/show_bug.cgi?id=8723 . This bug is the main cause of the above symptoms. (there are many other bug reports)
________________________________________
_______________Evidence_______________
This is a quote from chemist (Linux 2x debian stable 1x testing ) who can confirm this was a delay justification but the issue has by no means gone away and will never go away until you get a new device. Don’t plan on nokia to fix it as a bad widget will bring the issue right back again.
___________________________________
_______________My FIX – Idea points_______________
-Points of proposal-
1: Create a new hildon process called ‘hildon-widget’
2: Separate widgets from hildon-home completely
3: Layer of hildon-home and multiple instances of hildon-widget
4: Each individual widget owns an instance of hildon-widget and doesn't affect any other instance as currently a widget breaks, the whole phone breaks and a restart won’t fix it.
5: A widget using a instance of hildon-widget starts to break due to bugs, memory leaks, high CPU usage and hangs it auto restart’s a fresh copy of hildon-widget with the widget back on the screen automatically without the user being aware.
6: When a widget does crash and restarts itself, it dump’s information into an event log so it can easily be debugged or redeveloped. No more looking around for weeks on end.
Know what I mean? Maybe someone can code this? This just puts me off if I was a developer as I would be worried to develop widgets. Anything I develop might seriously hinder the device. It should be about promoting the open source community not scaring it into moving away from it. What are we supposed to do just not use widgets? Not make phone calls? Wait for the screen to stop showing a black screen before I answer a call? Re-launch the media widget every day??
Let’s face it Nokia will not fix this issue so it’s up to us. what do you guys think?? impossible?? nothing is impossible!!
_______________My FIX – Visual representation_______________
Last edited by felbutss; 2010-06-17 at 09:43.