LibX and Firefox e10s

[Luke Gaudreau]

Beginning with Firefox 48, Mozilla's multi-process feature, Electrolysis (e10s) will be enabled by default. At first the feature will roll out to a very small percentage of users, but over time it will ramp up. I have tested our LibX editions in Firefox Nightly with e10s enabled and wanted to report what I found.

• Searching Catalogs and Databases via the LibX toolbar works as expected.
• Shortcuts work as expected
• Reloading via EZProxy works as expected
• Searching for currently selected text via the right click menu DOES NOT work. The search is conducted with an empty string. This isn't too much of a surprise given that e10s separates the content and UI processes.

I'm wondering if others have tested LibX with e10s, or if there are plans for updating LibX to work correctly with it.

best,

Luke Gaudreau

Production Systems Librarian

Harvard University

[Godmar Back]

Would anyone be interested in porting LibX to FF/e10?

[kristin buxton]

I got a report from one of our faculty over the weekend about the frustration he's been having with LibX.  Is this related to the FF/e10 report noted last month, or is this likely a separate issue? Has active development on LibX stopped?  Should I find another solution for him?

"Is Libx ever going to be fixed for Firefox?

 It has been broken for a very long time, on Windows and on Linux. It
used to be perfectly fine, and then it broke last year.

The symptoms are that (1) Libx loads the memory in for *all* of the tabs
first, and then (2) then it reduces the memory requirements.

For anyone who uses Firefox in a "toy" method, in a nonserious way, with
perhaps fewer than ten tabs, then this is probably fine.

But for someone who has 500 tabs or more, like me, this is a big
problem. All that happens is that Libx 2.0 causes Firefox to crash, and
forget the tabs that you were saving.

Now, if you can actually get Firefox to load, then it actually reduces
the memory requirements.

But it does this in the wrong order -- first it loads in the memory, and
then it reduces the memory. So usually it will crash firefox instead.

I've been waiting for this to be fixed, but it's been over six months.

How do we get someone to fix this?

It used to be perfectly fine! "

Thanks,

Kristin

[Godmar Back]

We did one build for when Firefox started to require signatures but have not debugged anything since. The main developers currently use Chrome as their default browsers so there is little noticing at this point.

What you describe is absolutely possible wrt memory usage. Firefox has been a mess to develop for for a long long time.

We're calling for volunteers for FF development.

-- sent from my Nexus 5