747350 - Bookmarks sidebar very slow when primary X selection is remote via nxclient

Status: RESOLVED WORKSFORME

(Firefox :: Bookmarks & History, defect)

Description

[Tom Horsley]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0
Build ID: 20120313130407

Steps to reproduce:

I'm running nxclient to talk to my system at work remotely. I'm also running firefox. These are sibling processes on my local system, firefox is NOT running inside the nxclient. I have the bookmarks sidebar open in firefox.


Actual results:

If the primary X selection is currently held my a remote program running inside the nxclient (in other words, there will be lots of latency getting to the selection), then the bookmarks sidebar in firefox becomes very very slow and unresponsive. Expanding or collapsing items or clicking on a bookmark takes 20 or 30 seconds to react to the mouse click.


Expected results:

Since the bookmarks don't seem to have any need for the selection, I have no idea why they should be interacting with it at all. I'd expect them to be just as responsive no matter where the selection is located or how high the latency might be to get to it. I don't see anything like this in any other application I run, it is just the firefox bookmarks that display this behavior.

Comment 1

[Tom Horsley]

> currently held my a remote

Sorry, that should be: currently held *by* a remote

Comment 2

[Tom Horsley]

I first asked about this (with no results) in the forums:

http://forums.mozillazine.org/viewtopic.php?f=38&t=2093033

I should also note that the delay does indeed vanish if I run some application locally and grab the selection in it, so there is a 100% correlation between the location of the selection and the slow bookmarks.

Comment 3

[Wayne Mery (:wsmwk)]

Tom, do you still see this?

Comment 4

[Tom Horsley]

Well, I mostly use google-chrome these days, but the last time I tried firefox (not too many days ago) I saw the same thing.

Comment 5

[Wayne Mery (:wsmwk)]

rsx11m, are you able to reproduce?

Comment 6

[rsx11m]

I neither have NoMachine installed on my Linux box nor am I actually using Firefox - I'm a SeaMonkey guy, remember?  ;-)

Comment 7

[Mark Banner (:standard8)]

Unfortunately we don't have much information here to be able to fix an issue, so marking as WFM as we haven't had reports recently. We've also done a lot of changes over the last year or so that might be helping the issue.

If this is still an issue, please feel free to file a new bug, we also have ways in which we can profile what is going on and investigate issues.