624369 - "this._view.result is null" {file: "chrome://browser/content/places/controller.js" line: 179}]'

Status: RESOLVED WORKSFORME

(Firefox :: Bookmarks & History, defect)

Description

[Carsten Book [:Tomcat]]

Steps to reproduce:
-> Beta9 build german
-> Click on show all bookmarks on linux and mac version

--> Fehler: An error occurred updating the cmd_selectAll command: [Exception... "'[JavaScript Error: "this._view.result is null" {file: "chrome://browser/content/places/controller.js" line: 179}]' when calling method: [nsIController::isCommandEnabled]"  nsresult: "0x80570021 (NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)"  location: "JS frame :: chrome://global/content/globalOverlay.js :: goUpdateCommand :: line 55"  data: yes]
Quelldatei: chrome://global/content/globalOverlay.js
Zeile: 61

Comment 1

[Marco Bonardo [:mak]]

is this still an issue in final?

Comment 2

[Serge Gautherie (:sgautherie)]

Another example:

1. Run "... --browser-chrome --test-path=browser/components/places/tests/browser/browser_library_views_liveupdate.js"

[Mozilla/5.0 (Windows NT 5.0; rv:2.0b13pre) Gecko/20110316 Firefox/4.0b13pre] (mozilla-central-win32/1300282333)
(http://hg.mozilla.org/mozilla-central/rev/4f07bebb993b)

reports this error.

[Mozilla/5.0 (Windows NT 5.0; rv:2.0pre) Gecko/20110330 Firefox/4.0pre] (mozilla-2.0-win32/1301536603)
(http://hg.mozilla.org/releases/mozilla-2.0/rev/70e0a1a2da21)

does not report this error (anymore).

R.WorksForMe.

Comment 3

[Serge Gautherie (:sgautherie)]

Mozilla/5.0 (Windows NT 5.0; rv:2.0pre) Gecko/20110328 Firefox/4.0pre
20110328030204
http://hg.mozilla.org/releases/mozilla-2.0/rev/c5e4090374e6

still reported this error.

Mozilla/5.0 (Windows NT 5.0; rv:2.0pre) Gecko/20110329 Firefox/4.0pre
20110329030203
http://hg.mozilla.org/releases/mozilla-2.0/rev/c5e4090374e6

doesn't anymore.

But these nightlies are built from the same revision:
there was no new changeset between 24th and 30th :-<

NB: Comparing files from these (zip) builds, shows a few differences in 3 .chk, 22 .dll, 5 .exe (and 2 .ini) files :-|

***

Fwiw, I checked
http://hg.mozilla.org/build/buildbotcustom/pushloghtml?startdate=2011-03-28&enddate=2011-03-30
and
http://hg.mozilla.org/build/buildbot-configs/pushloghtml?startdate=2011-03-28&enddate=2011-03-30
but I don't see anything related there.

I have no idea about what (changed and) fixed this (on m-2.0 branch) :-(

Comment 4

[Serge Gautherie (:sgautherie)]

Mozilla/5.0 (Windows NT 5.0; rv:2.2a1pre) Gecko/20110328 Firefox/4.2a1pre
20110328125522
http://hg.mozilla.org/mozilla-central/rev/df9338ea288b

still reported this error.

Mozilla/5.0 (Windows NT 5.0; rv:2.2a1pre) Gecko/20110329 Firefox/4.2a1pre
20110329030437
http://hg.mozilla.org/mozilla-central/rev/79487686ac29

doesn't anymore.

Fix timeframe would be
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=df9338ea288b&tochange=79487686ac29
but I'm not sure whether these changesets are related either.

NB: Same file differences, plus omni.jar (which can't be opened).

***

I wonder what m-2.0 and m-c have in common that could have been fixed that day.

Comment 5

[Serge Gautherie (:sgautherie)]

(In reply to comment #2)
> 1. Run "... --browser-chrome
> --test-path=browser/components/places/tests/browser/browser_library_views_liveupdate.js"

Damn it: as this happens to me once in a while, when it does not make sense try (even) harder.

Disregard my comments 2 to 4:
actually, I can trigger this "random" error when running this test, with both m-2.0 and m-c builds of the 29th :-|

***

And SeaMonkey 2.0/2.2 has the same bug.

Comment 6

[Serge Gautherie (:sgautherie)]

(In reply to comment #5)
> And SeaMonkey 2.0/2.2 has the same bug.

Arf: SeaMonkey 2.1/2.2!

Comment 7

[Serge Gautherie (:sgautherie)]

(In reply to comment #2)
> Another example:
> 
> 1. Run "... --browser-chrome
> --test-path=browser/components/places/tests/browser/browser_library_views_liveupdate.js"


Same with
--browser-chrome
--test-path=suite/common/places/tests/browser_library_infoBox.js

Comment 8

[Mark Banner (:standard8)]

I've not seen this recently and I just tested a couple of runs of browser_library_views_liveupdate.js and I can't see it. Therefore marking as WFM, I assume its been fixed sometime in the last few years.