485546 - moving a search engine on manage search engines takes 5 minute delay - too slow

Status: RESOLVED DUPLICATE of bug 483121

(Firefox :: Search, defect)

Description

[Charles Evans]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.7) Gecko/2009021906 Firefox/3.0.7
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.7) Gecko/2009021906 Firefox/3.0.7

I have 47 search plugins. If I change the order moving 3 or 4 search plugins, firefox freezes when I close the window for about 5 minutes with near 100% CPU use.

Reproducible: Always

Steps to Reproduce:
1. Add over 40 search engines
2. Move 4 from bottom to top
3. watch the clock
Actual Results:  
Freeze for 5min+

Expected Results:  
No freeze at all

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Charles, could you have a look at your profile, zip all the search plugins which are located under the searchplugins folder, and send them to me via email? It would be great to have the exact same search plugins for my test.

Comment 2

[:Gavin Sharp [email: [e-mail]]]

The engine manager code isn't exactly optimized, because in the common cases people typically have 10 or fewer search engines.

See also bug 363970 and bug 483121.

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Attachment: testcase (list of search engines)

Sorry for the delay. Here a list of around 40 search engines which demonstrate the slow-down when moving a couple of them around inside the Search Engine Manager.

Comment 4

[chakolate47]

I have the same problem, with only 8 engines.  I thought it wasn't working at all, but now that I wait 2-5 minutes, the manager will move engines up or down.  

FYI, I get the same result in Safe Mode.

Comment 5

[Florian Quèze [:florian]]

The 'manage search engine dialog' no longer exists (no longer visible since bug 1088660, and completely removed since bug 1119250). It's possible the underlying performance problem still exists in the new search preferences code, but I think bug 483121 covers the code issues we need to investigate in a more technical way, so I'm marking as a duplicate.