Closed Bug 1248956 Opened 8 years ago Closed 6 years ago

"NS_ERROR_ILLEGAL_VALUE: Invalid arguments" error while selecting recently bookmarked folder from Library

Categories

(Firefox :: Bookmarks & History, defect, P3)

defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox44 --- wontfix
firefox45 --- wontfix
firefox46 --- wontfix
firefox47 --- wontfix

People

(Reporter: vtamas, Unassigned)

References

Details

(Keywords: regression)

[Affected versions]:
Firefox 44.0.2
Firefox 45 Beta 6 
Firefox 46.0a2 (2016-02-16)
Firefox 47.0a1 (2016-02-16)

[Affected platforms]:
Ubuntu 12.04 64-bit
Mac 10.10.5
Windows 10 32-bit

[Steps to reproduce]:
1.Launch Firefox with clean profile.
2.Bookmark a webpage.
3.From the toolbar, click the Bookmarks Menu button.
4.Select "Show All Bookmarks".
5.Expand the "Bookmarks Menu" entry and click "Recently Bookmarked" or "Recent Tags".
6.Check the browser console.

[Expected Results]:
There are no errors thrown in Browser Console.


[Actual Results]:
The following error is thrown in Browser console while clicking on “Recently Bookmarked” and “Recent Tags” folders:
NS_ERROR_ILLEGAL_VALUE: Invalid arguments nsLivemarkService.js:299:0
 

[Additional notes]:
Running the above steps in Firefox 32.0a1 (2014-06-01) appears another error in Browser Console “uncaught exception: 2147942487”.
it's a call to getLivemark(), likely coming from browser/components/places/content/treeView.js

Should be debugged to get a proper js stack
Priority: -- → P3
This error is thrown as "NS_ERROR_ILLEGAL_VALUE: Invalid arguments" format since Firefox 40.0a1 from 2015-04-28.

So, I suspect that this error is caused by Bug 1094900 (https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=5fa88d413c4f6154cf10eb4a99a4a5d66e03e544&tochange=ad388474898c9ce2d288dc9b802ef6dec86088b0)
Blocks: 1094900
Keywords: regression
This WFM on a fresh profile, I suspect we solved it with one of the refactors over the last year or two.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.