Again, there's no such thing as "microbrowser". It's MicroB. . . .

Me, I've never once experienced the issue you're talking about. :\

By the way, if this issue is so "common" has anybody bothered to file a bug?

Yes, someone has. And thanks for reminding me; I just voted for it.

Hi;

Thanks General for correcting me re: MicroB. Correct terminology is essential for clear communication.

I've spent several hours working on this problem.Its very tedius, given the way MicroB constantly stalls, and the very annoying several minute delay waiting for the about:config dialog to come up.

When the browser stalls, top shows between 90 and 99% utilization. The following screen shot was taken while waiting 4 minutes, 33 seconds for a response from about:config :


1.) The problem does not require a MicroB crash as a trigger, but a crash or 'killing' a slow MicroB instance almost always induces it.
2.) When it occurs, tthe folowing is present in ~/.mozilla/microb/prefs.js:

user_pref("security.warn_entering_secure", true);
user_pref("security.warn_leaving_secure", true);
user_pref("security.warn_submit_insecure", true);

3.) Changing them to this will correct the problem until the next ocurrence:
user_pref("security.warn_entering_secure",false);
user_pref("security.warn_leaving_secure",false);
user_pref("security.warn_submit_insecure",false);

This makes me hopeful that if I can run some kind of a script to launch the MicroB, that will force those values in and then do the launch; I can use my n810 with going cRAzY until the bug is fixed. However, that is beyond my newbie skils...

What if you create /home/user/.mozilla/microb/user.js
file and add your preferences there.
At least it works with Mozilla Firefox. If user.js exist
it precedes prefs.js. I don't know if MicroB supports user.js