Ask / Submit

browser crash when using 4G in [answered]

asked 2017-04-14 21:39:14 +0300

silta gravatar image

updated 2017-04-17 15:58:48 +0300

After updating my Jolla1 to I noticed browser crashes in 9 out of 10 cases when loading homepage after launching. After a while I saw that mobile data preferences changed from preferred 3G to preferred 4G during update process.

Changing back to 3G solved the problem. Crashes happen only in 4G.

I don`t know, if it is related to this post about crashes in but it is the same behavior.

EDIT 2017-04-15 From today browser crashes also happened on 3G and Wifi. Removing homepage and starting with blank page doesn't help.

I tried to launch browser via terminal and got the following output, I don't have the knowledge to interpret this text. Any advice?

[nemo@Sailfish ~]$ sailfish-browser
[D] unknown:0 - Using Wayland-EGL
greHome from GRE_HOME:/usr/bin is not found, in /usr/bin/
Created LOG for EmbedLite
[W] unknown:0 - Could not find any zN.M subdirs!
[W] unknown:0 - Theme dir "/usr/share/themes/jolla-ambient/meegotouch/z1.0/" does not exist
[D] onCompleted:103 - ViewPlaceholder requires a SilicaFlickable parent
Loaded xulDir:/usr/lib/xulrunner-qt5-38.8.0/, appDir:/usr/bin
EmbedLiteExt virtual nsresult EmbedChromeManager::Observe(nsISupports*, const char*, const char16_t*):82: obj:(nil), top:app-startup
EmbedLiteExt virtual nsresult EmbedTouchManager::Observe(nsISupports*, const char*, const char16_t*):86: obj:(nil), top:app-startup
EmbedLiteGlobalHelper app-startup
EmbedLiteSyncService app-startup
EmbedPrefService app-startup
EmbedliteDownloadManager initialized
UserAgentOverrideHelper app-startup
1492258883601   addons.manager  DEBUG   Application has been upgraded
1492258883706   addons.manager  DEBUG   Loaded provider scope for resource://gre/modules/addons/XPIProvider.jsm: ["XPIProvider"]
1492258883722   addons.manager  DEBUG   Loaded provider scope for resource://gre/modules/LightweightThemeManager.jsm: ["LightweightThemeManager"]
1492258883743   addons.manager  DEBUG   Loaded provider scope for resource://gre/modules/addons/GMPProvider.jsm
1492258883756   addons.manager  DEBUG   Loaded provider scope for resource://gre/modules/addons/PluginProvider.jsm
1492258883767   addons.manager  DEBUG   Starting provider: XPIProvider
1492258883770   addons.xpi      DEBUG   startup
1492258883778   addons.xpi      DEBUG   checkForChanges
1492258883784   addons.xpi      DEBUG   Loaded add-on state from prefs: {}
1492258883789   addons.xpi      DEBUG   getInstallState changed: false, state: {}
1492258883812   addons.xpi-utils        DEBUG   Opening XPI database /home/nemo/.mozilla/mozembed/extensions.json
1492258883814   addons.xpi-utils        DEBUG   Rebuilding XPI database with no extensions
1492258883817   addons.xpi      DEBUG   No changes found
1492258883819   addons.manager  DEBUG   Registering shutdown blocker for XPIProvider
1492258883822   addons.manager  DEBUG   Provider finished startup: XPIProvider
1492258883822   addons.manager  DEBUG   Starting provider: LightweightThemeManager
1492258883823   addons.manager  DEBUG   Registering shutdown blocker for LightweightThemeManager
1492258883826   addons.manager  DEBUG   Provider finished startup: LightweightThemeManager
1492258883827   addons.manager  DEBUG   Starting provider: GMPProvider
1492258883837   addons.manager  DEBUG   Registering shutdown blocker for GMPProvider
1492258883840   addons.manager  DEBUG   Provider finished startup: GMPProvider
1492258883841   addons.manager  DEBUG   Starting provider: PluginProvider
1492258883842   addons.manager  DEBUG   Registering shutdown blocker for PluginProvider
1492258883844   addons.manager  DEBUG   Provider finished startup: PluginProvider
1492258883845   addons.manager  DEBUG   Completed startup sequence
Created LOG for EmbedPrefs
[D] QMozWindowPrivate::setSize:71 - Trying to set empty size:  QSize(-1, -1)
Attempting load of
EmbedLiteExt virtual nsresult EmbedTouchManager::Observe(nsISupports*, const char*, const char16_t*):86: obj:0x4695ca40, top:domwindowopened
EmbedLiteExt void EmbedChromeManager::WindowCreated(nsIDOMWindow*):91: WindowOpened: 0x4695ca50
EmbedLiteExt void EmbedTouchManager::WindowCreated(nsIDOMWindow*):95: WindowOpened: 0x4695ca50
EmbedLiteExt void EmbedTouchManager::WindowCreated(nsIDOMWindow*):108: id for window: 1
###################################### SelectAsyncHelper.js loaded
###################################### embedhelper.js loaded
### ContextMenuHandler.js loaded 
### SelectionPrototype.js loaded
### SelectionHandler.js loaded
Init Called:[object Object]
Segmentation fault
[nemo@Sailfish ~]$

For more Information, here the output of journalctl. I put it into an text file because of the 183 lines :)


edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by silta
close date 2017-04-17 15:56:16.780282


My crashes have all been on wifi.

DaveRo ( 2017-04-15 10:42:08 +0300 )edit

My browser crashed today while using 3G ( I have Intex, modded to jolla C with software) . I was signing in to this service. After clicking sign in page started blink fast and after couple seconds browser shuts down. It took a while before I could restart browser. That Blinking had also happened couple times before update.

MJolla ( 2017-04-15 11:47:53 +0300 )edit

I had the same experience during the first couple of hours after OS upgrade. Then the browser seems to behave normally. Maybe because of my daily BTRFS balance?

objectifnul ( 2017-04-15 22:21:44 +0300 )edit

Btrfs-balancer allocation returns 70% allocated. I can't believe that's the reason. BTW browser is the only app not working. All the other apps and the whole OS are working fine. The OS update was three days ago.

silta ( 2017-04-16 00:29:33 +0300 )edit

@silta - I hope you don't mind, I took the liberty of pasting your code. You're right, at first it didn't format properly, but, I then moved (from the 2nd line onwards) each line 4 spaces inwards from the left side.

Having time to look back at your code and then trying it myself, yields the same code output as yours, but in my case, the browser does open and functions correctly. You're seeing this only because of the way you chose to launch the application. I don't believe this is anything to do with your problem. I did this using 3G, also ran the same tests using 4G.

Perhaps to simply remove sailfish-browser pkcon remove sailfish-browser then reinstall with pkcon install sailfish-browser. By doing this, you will lose your favourites.

fmotl ( 2017-04-16 02:18:40 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2017-04-17 14:45:49 +0300

Nekron gravatar image

This is what fixed random crashes on sailfish browser startup for me on four devices (2x J1, 1x JC, 1x JT) after latest update:

  • enable developer mode or install File Browser application
  • close sailfish browser
  • open terminal and move .mozilla directory (mv .mozilla .mozilla_bak)
  • alternative enable hidden files in File Browser settings and rename .mozilla into .mozilla_bak
  • launch sailfish browser and enjoy stable startup w/out crashes
edit flag offensive delete publish link more


Thanks a lot. It solved my problem too :)

silta ( 2017-04-17 15:55:03 +0300 )edit

Excellent answer! @Nekron

fmotl ( 2017-04-17 16:01:55 +0300 )edit

Question tools



Asked: 2017-04-14 21:39:14 +0300

Seen: 464 times

Last updated: Apr 17