Blackberry 10 OS/Browser: Poor Application Isolation?
So I recently ported over my Playbook Webworks app over to the BB10. The app is somewhat data intensive (stores a large webdatabase locally). I finished it, loaded it onto my BB10 Dev Alpha, and to test how much my app might lag other applications, I fired up the Browser.
It was horrendous. The browser started artifacting and glitching up. This shows that there is poor isolation between applications and I'm hoping that this is only because the Dev Alphas are running on Dev code and not final code. Hopefully issues like this are fixed, because I certainly don't want a rogue app to be messing up the browser while I'm doing my banking, or something like that.
Going back to my own app, the keyboard glitched up along with the whole OS and the keyboard because squeezed to half and the other half was just black. It stayed like that until I rebooted the Dev Alpha. This also shows the OS is not completely finished yet and there's probably a lot of fixing required in the coming weeks. Hopefully the OS will be completely finished in time for Feb launch.
- CrackBerry Addict
12-17-12, 12:24 PM #4
- 522 Posts
I have a feeling that you're app is not a good citizen when it comes to true multitasking and freeing some resources while in the background. Even on a PC this becomes a problem with very data and resource intensive apps. It's not a problem with the OS, it's the compromise that has to be made between limited resources on any given machine being shared between all running processes. I believe it's also a problem with selfish coders that don't think that they should give up resources when they aren't needed so that other apps can run well. That's one thing that iOS and Android don't have to worry about because they don't run true multitasking with active background processes. It happens on all platforms where true multitasking happens. It's not your fault, just how the most recent generation of coders have been taught.
- CrackBerry Addict
12-17-12, 01:11 PM #6
- 522 Posts
OP, I'm sorry for singling you out, but I hope you understand the intent of my post. While you admit that your app is very data intensive, you do not say what kind of resources you are using while it's in the background doing whatever it does. This is where I believe there is a lack of understanding when it comes to good programming practices. I just ask that before you cast stones at the OS, you make 100% sure that you are doing your due diligence in consolidating and freeing your resources when your app does not have focus.
- 12-17-12, 02:07 PM #7
Also, your app doesn't use the run_when_backgrounded permission, does it? If it does not, then there's really little excuse for that sort of result, contrary to ffejrobins30's suggestions (which are valid if you are using that restricted feature). The OS should be rock-solid enough to avoid such things, and as long as you're not consuming most of the memory in the system it doesn't seem anyone could point to your app and blame it for messing up the system. QNX is better than that (in released/final versions, anyway).
Have you enabled the "diagnostic overlay" to see what sort of resource usage your app causes? That's the top-left swipe thing that you can easily google to learn more about...
- 12-17-12, 05:18 PM #8
The HTML5 test - How well does your browser support HTML5?
Most likely you were using older and less efficient ways to do certain things because the Playbook didn't have them.
But regardless, it certainly shouldn't mess up the keyboard:
Picture with the keyboard only showing half of it. (I believe when I took the screenshot the keys/numbers were actually showing, that might not have gotten captured)
And it also shouldn't cause artifacting in other apps, though the browser app likely has shared resources with any webworks app.
- 12-18-12, 02:36 AM #10
But my point is that you claimed that your webworks app is a database intensive app that writes a lot of data to the device --- so you have 2 likely potential bottleneck issues. The first potential bottleneck is the actually writing of data to the device --- which BB10 webworks have now better File API access to directories and systems. The second potential bottleneck is the database itself --- which RIM has now incorporated indexed db into their system.
If you attempt to write a lot of data using a less efficient method --- it is going to affect other apps that are running at the same time. Even on a desktop PC, if you transfer massive amount of data using an older method (maybe IDE instead of SATA), other programs that are running may stutter.
- By maximer28 in forum General BlackBerry DiscussionReplies: 9Last Post: 09-26-12, 10:02 AM
- By varunsain in forum BlackBerry 10 OSReplies: 1Last Post: 08-10-12, 02:29 AM
- By CHIP72 in forum General BlackBerry DiscussionReplies: 16Last Post: 06-05-12, 02:55 PM
- By modine in forum BlackBerry PlayBookReplies: 17Last Post: 02-13-12, 09:08 PM