[jonasahlgren]

Hi!
I was investigating if mobiOne could be used as tool for developing my webkit mobile web applications. Look very promising but when I fire up my web app i noticed that a MobiOne process goes mad and takes almost all my CPU power. Checking my access_log I see that the mobiOne browser fetches my first included javascript file over and over again. Looks like it is caught in some never ending loop. The web app works but is extremely slow. I must exit the both design center and testcenter to make it stop (and be able to do anything else). I do not get this behaviour when running the same webapp in Safari. This happens in version 1.0 m8.

Anyone knows why this is?

/Jonas

[freerunnering]

Have you updated to M-8 update 1 as that fixes bugs in the first release of M-8?

[wayne]

jonasahlgren,

We have not seen the problem you describe before. Is it possible for you to share your webapp URL or code with me or provide a small example of the issue? I’m sure we can isolate the problem quickly once we can replicate it. If yes, you can send it to my attention (Wayne) at mailto:support@genuitec.com

Wayne
Genuitec Mobile Team

[wayne]

jonasahlgren followed up with me. Following are the details he provided:

Hi!

I have investigated some more and now I can reproduce it. I think this
problem occurs when you are using the cache oppertunities in html5 (
http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html).
Here is what I need to do to trigger the hang.

1. I access my index.html file in Mobione by entering the url in the
browser. The index.html is served by my tomcat appserver (that runs locally)
and the index.html points out a manifest file that includes my resources to
be cached. The webapp loads fine and I can see that it fetches all my
resources (which is expected since this is the first hit to the server).
2. I reload the url in the browser and I can see in my log that all my
resources is not fetched again due to the caching. This is what I want. So
far so good.
3. I modify the manifest file (a comment change is enough) to trigger the
browser to refetch all resources.
4. When I now reload the url in the browser the browser checks the manifest
file and recognized the change (gets HTTP 200), then mobiOne browser goes
mad by trying to download the index.html over and over again (maxes out cpu).
Sometimes it hangs on index.html, sometimes it hangs on the first included
javascript file.
5. I now need to exit mobiOne to get my cpu back. If I start Mobione again
and enter the url I will come to step 3 (goes mad) even if I clear the
cache. Seems like there are something cached in mobiOne browser that you
cannot clear?

I think no point handing you a url to my webapp since I need to update the
manifest file on the server to make this happen. I use M8, update 1.

The exact same scenario works fine in Safari.

Hope you can reproduce it and get back to me what the problem is.

Thanks

[jonasahlgren]

Just one correction to the prevoius post..Step 5. When I start Mobione again (and enter the URL) I come to step 4 (not step 3)

/Jonas Ahlgren

[wayne]

Update:

We have been trying to replicate this CPU pegging experience with no success. We have been testing on single and multicore HW to see if there is something at that level that we overlooked. Still no luck replicating the problem.

Would it be possible for you to provide us an example webapp to test with, e.g., a URL (preferred) or WAR to test with?

Wayne
Genuitec Mobile Team

[Author]

Posts