Here is another question of mine that has bothered me for a long time.
During the invocation of TB |make mozmill| test suite by running locally
produced DEBUG version of C-C test, I have seen the following WARNING
messages in the log regarding "Chrome file doesn't exist".
I checked the bugzilla this time around, but
I don't think anybody mentioned the following messages I observed.
Found mentions in bugzilla:
612796 Chrome file doesn't exist:
$OBJDIR/_tests/reftest/reftest/chrome/reftest/content/autoconf.js
2010-11-16
1105713 "Chrome file doesn't exist head.js" in tests 2014-12-23
762842 Chrome file doesn't exist: mozapps/update/warning.gif 2012-06-09
954129 Chrome file doesn't exist: branding/icon48.png 2013-12-29
1133261 Chrome file doesn't exist: …/mailCore.js 2015-02-14
1191778 Chrome file doesn't exist:
.../NightlyDebug.app/Contents/Resources/chrome/toolkit/content/mozapps/preferences/preferences.css
2015-08-24
6 bugs found.
From the summary in my log:
Again the number at the beginning of each line indicates the frequency
of occurences.
Please note that the most frequent (132)WARNING message had "null" as
its last component of
the file path. I suspect there is something wrong in the code.
I suspect a null pointer is passed and "null" is produced as the result
in the pathname, but I am not sure.
The second most frequent message refers to dropbox.png (!?).
Yers, I have dropbox installed, but how does TB know about it and why it
wants to access dropbox icon or something?
Some names such as notifyPluginBlocked.png
suggests we are missing an important icon for notifying the user that
some plugin update status (this case "blocked")?
========================================
Chrome file doesn't exist
========================================
132 Chrome file doesn't exist:
/NREF-COMM-CENTRAL/objdir-tb3/dist/bin/chrome/messenger/content/messenger/messengercompose/null
100 Chrome file doesn't exist:
/NREF-COMM-CENTRAL/objdir-tb3/dist/bin/chrome/classic/skin/classic/messenger/icons/dropbox.png
35 Chrome file doesn't exist:
/NREF-COMM-CENTRAL/objdir-tb3/dist/bin/chrome/toolkit/skin/classic/global/icons/information-64.png
2 Chrome file doesn't exist:
/NREF-COMM-CENTRAL/objdir-tb3/dist/bin/chrome/toolkit/skin/classic/mozapps/plugins/notifyPluginOutdated.png
2 Chrome file doesn't exist:
/NREF-COMM-CENTRAL/objdir-tb3/dist/bin/chrome/toolkit/skin/classic/mozapps/plugins/notifyPluginBlocked.png
2 Chrome file doesn't exist:
/NREF-COMM-CENTRAL/objdir-tb3/dist/bin/chrome/classic/skin/classic/messenger/messengercompose/compose-toolbar.png
2 Chrome file doesn't exist:
/NREF-COMM-CENTRAL/objdir-tb3/dist/bin/chrome/classic/skin/classic/messenger/icons/mail-toolbar-small.png
1 Chrome file doesn't exist:
/NREF-COMM-CENTRAL/objdir-tb3/dist/bin/chrome/toolkit/skin/classic/mozapps/extensions/stripes-info-negative.png
Again, any sensible explanation why these are accessed (especially the
dubious "null" file name at the top) is appreciated.
This is tested under Debian GNU/Linux 64-bit (aka amd64) version.
If I can get rid of 200- warning lines, so much the better.
TIA
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
