1113166 - Startup assertion failure: can't find built-in stylesheet file resource://gre-resources/counterstyles.css

Status: RESOLVED DUPLICATE of bug 1303764

(Firefox Build System :: General, defect)

Description

[Alex Wafula]

I've built Firefox with instructions from here: https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Source_Code/Mercurial/Bundles with the exception of:

[trusted]
groups = root
users = root

Adding the above here: /etc/mercurial/hgrc.d/trust.rc as explained in bug 1112075

On using ./mach run to launch Firefox, it crashes with the following response on the terminal:

(process:19641): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
[19641] ###!!! ABORT: LoadSheetSync failed with error 80520012 loading built-in stylesheet 'resource://gre-resources/counterstyles.css': file /media/waltz/devs/mozilla/mozilla-central/layout/style/nsLayoutStylesheetCache.cpp, line 374
[19641] ###!!! ABORT: LoadSheetSync failed with error 80520012 loading built-in stylesheet 'resource://gre-resources/counterstyles.css': file /media/waltz/devs/mozilla/mozilla-central/layout/style/nsLayoutStylesheetCache.cpp, line 374

Comment 1

[(not currently active) Ted Mielczarek]

I would hazard a guess that something went wrong in your build--that's a failsafe assertion about finding a required data file. Did you have any strange output from the build? Can you try a top-level rebuild (./mach build) and see if that fixes it?

Comment 2

[Alex Wafula]

I'm still getting the same error after rebuilding with ./mach build

The only problem I had during my initial build process was when running hg pull, I got "not trusting file ~/mozilla-central/.hg/hgrc" until I changed a couple of stuff as explained in bug 1112075

Comment 3

[Niels De Graef]

I have the same problem, anyone any idea as to what it might be?

Comment 4

[(not currently active) Ted Mielczarek]

This file is supposed to be copied to the objdir during the build, and clearly something has gone wrong or the build didn't succeed. If I look at this file in an objdir where I just did a successful build I see:
$ ls -l debug-mozilla-central/dist/bin/chrome/toolkit/res/counterstyles.css
lrwxrwxrwx 1 luser luser 53 Aug 19 10:20 debug-mozilla-central/dist/bin/chrome/toolkit/res/counterstyles.css -> /build/mozilla-central/layout/style/counterstyles.css
$ ls -l /build/mozilla-central/layout/style/counterstyles.css
-rw-rw-r-- 1 luser luser 11589 Jul 16 12:24 /build/mozilla-central/layout/style/counterstyles.css

Does that file exist at that location ($objdir/dist/bin/chrome/toolkit/res/counterstyles.css) in your build?

Comment 5

[Niels De Graef]

Yes, in both locations, the file exists.

Comment 6

[Niels De Graef]

Some more info: mach package also doesn't work. This is what it returns:

 0:01.10 /usr/bin/make -C . -j4 -s -w package                       
 0:01.14 make: Map '/data/workspace/comm-central/obj-x86_64-unknown-linux-gnu' wordt binnengegaan
 0:01.58 make[1]: Map '/data/workspace/comm-central/obj-x86_64-unknown-linux-gnu/mail/installer' wordt binnengegaan
 0:01.76 make[2]: Map '/data/workspace/comm-central/obj-x86_64-unknown-linux-gnu/mail/installer' wordt binnengegaan
 0:01.88 make[3]: Map '/data/workspace/comm-central/obj-x86_64-unknown-linux-gnu/mail/installer' wordt binnengegaan
 0:07.81 Executing /data/workspace/comm-central/obj-x86_64-unknown-linux-gnu/dist/bin/xpcshell -g /data/workspace/comm-central/obj-x86_64-unknown-linux-gnu/dist/bin/ -a /data/workspace/comm-central/obj-x86_64-unknown-linux-gnu/dist/bin/ -f /data/workspace/comm-central/mozilla/toolkit/mozapps/installer/precompile_cache.js -e precompile_startupcache("resource://gre/");
 0:07.98 Traceback (most recent call last):
 0:07.98   File "/data/workspace/comm-central/mozilla/toolkit/mozapps/installer/packager.py", line 407, in <module>
 0:07.98     main()
 0:07.98   File "/data/workspace/comm-central/mozilla/toolkit/mozapps/installer/packager.py", line 401, in main
 0:07.98     args.source, gre_path, base)
 0:07.98   File "/data/workspace/comm-central/mozilla/toolkit/mozapps/installer/packager.py", line 159, in precompile_cache
 0:07.98     errors.fatal('Error while running startup cache precompilation')
 0:07.98   File "/data/workspace/comm-central/mozilla/python/mozbuild/mozpack/errors.py", line 103, in fatal
 0:07.98     self._handle(self.FATAL, msg)
 0:07.98   File "/data/workspace/comm-central/mozilla/python/mozbuild/mozpack/errors.py", line 98, in _handle
 0:07.98     raise ErrorMessage(msg)
 0:07.98 mozpack.errors.ErrorMessage: Error: Error while running startup cache precompilation
 0:08.00 /data/workspace/comm-central/mozilla/toolkit/mozapps/installer/packager.mk:41: recept voor doel 'stage-package' is mislukt
 0:08.00 make[3]: *** [stage-package] Fout 1
 0:08.00 make[3]: Map '/data/workspace/comm-central/obj-x86_64-unknown-linux-gnu/mail/installer' wordt verlaten
 0:08.00 /data/workspace/comm-central/mozilla/toolkit/mozapps/installer/packager.mk:86: recept voor doel 'make-package' is mislukt
 0:08.00 make[2]: *** [make-package] Fout 2
 0:08.00 make[2]: Map '/data/workspace/comm-central/obj-x86_64-unknown-linux-gnu/mail/installer' wordt verlaten
 0:08.00 /data/workspace/comm-central/mozilla/config/rules.mk:549: recept voor doel 'default' is mislukt
 0:08.00 make[1]: *** [default] Fout 2
 0:08.00 make[1]: Map '/data/workspace/comm-central/obj-x86_64-unknown-linux-gnu/mail/installer' wordt verlaten
 0:08.00 /data/workspace/comm-central/mozilla/../mail/build.mk:10: recept voor doel 'package' is mislukt
 0:08.00 make: *** [package] Fout 2
 0:08.00 make: Map '/data/workspace/comm-central/obj-x86_64-unknown-linux-gnu' wordt verlaten

Comment 7

[(not currently active) Ted Mielczarek]

Ok, maybe sanity check that the toolkit.manifest is written properly?
$ grep gre-resources /build/debug-mozilla-central/dist/bin/chrome/toolkit.manifest 
resource gre-resources toolkit/res/

and that it's referenced from the top-level chrome.manifest:
$ grep toolkit /build/debug-mozilla-central/dist/bin/chrome.manifest  
manifest chrome/toolkit.manifest

Comment 8

[Niels De Graef]

$ grep gre-resources obj-x86_64-unknown-linux-gnu/dist/bin/chrome/toolkit.manifest 
resource gre-resources toolkit/res/

$ grep toolkit obj-x86_64-unknown-linux-gnu/dist/bin/chrome.manifest                                    
manifest chrome/toolkit.manifest
manifest components/toolkitplaces.manifest
manifest components/toolkitsearch.manifest

Comment 9

[Niels De Graef]

Might be a duplicate of bug 1002002 ?