User Agent: Mozilla/5.0 (Windows NT 5.1; rv:47.0) Gecko/20100101 Firefox/47.0 Build ID: 20160212030242 Steps to reproduce: Bumping https://bugzilla.mozilla.org/show_bug.cgi?id=851133 I added several comments to 851133 but I'm not sure if my problem is a duplicate or not, althought the sympthoms are the same, the reasons may be different. Also I don't know if 851133 is still active or not as it is old and has: a needinfo flag and the author is gone for 3 years, the author has Mac + firefox 17, I have Windows XP + Firefox Nightly 47.0a1, and a code the author has posted doesn't reproduce on me. . Mozilla developers are free to decide if this is a duplicate or not.
tracking-e10s: --- → ?
OS: Unspecified → Windows XP
Hardware: Unspecified → x86
Bug 851133 is not about e10s. If your issue is gone with e10s disabled, it's a different bug.
marcino, Please attach a full copy of your about:support, including the list of add-ons you have installed when encountering this bug. Preferably, run with a completely fresh profile with no add-ons installed in that profile. Thank you.
Flags: needinfo?(twalker) → needinfo?(marcino245)
TracyWalker, I think that you did not notice that I already mentioned that > I made a fresh profile, but that did not help and a fresh profile has no add-ons installed. But if you have noticed that and despite this you still for some other reasons need a full copy of about:support of my fresh profile, let me know.
yes, please provide full about:support
marcino, this comment you made in bug 851133 hints at some sort of performance hold up; "The text input freezes and also the char indicator dissapear and when I switch to another tab and back after several seconds, the problem dissapears." Could you double check the freeze with your add-ons disabled vs enabled. Is it better or worse with add-ons disabled.
Hey, at the moment the bug seems to be "gone" even on my private profile (with many add-ons enabled) + "multi-process" enabled (so I have it enabled), but as it is a random bug, I don't know what fixed it and I don't know if it is gone for sure. So I am just gonna wait a week, and if the bug won't come back, I will close it. And what could trigger the bug to get fixed? Hell knows as several actions happened already like: - I disabled broken UnMHT which was causing "switching between tabs url" problem (bug 1248120), so UnMHT could also cause Text input element becomes unresponsive to text input #2 - there were several Nighty updates, it is possible that any of them could fix the bug
Hmm, yes, it could be it's just not reliably reproducing. Could be that something landed in a recent Nightly that fixed this issue. If your curious about the later. you can use mozregression to find the fix window. :) I am going to remove tracking-e10s: ?. Please reset it, if you determine this is still occurring for you reliably without add-ons enabled. Thanks for your efforts in reporting, tracking down and checking on your bugs.
OK. Thanks you too for your efforts in developing Firefox and fixing bugs.
I realized just now, that the first reason (disabling UnMHT) is invalid (bogus) as an explanation for this bug, just a mistake, ignore it, as I have been experiencing the bug also on a fresh profile (no add-ons), therefore it had to be most likely the second reason: > - there were several Nighty updates, it is possible that any of them could fix the bug as disabling multi-process was causing the bug to dissapear but it also could be anything like something in Windows that has been disrupting Firefox and is gone now, or whatever else. It is hard to determine what was the cause as that was a random issue appearing on many random websites (those that I do not remember exactly) and is hard to reproduce. I rerun a single Nightly 13.02.2016 (a first time the bug has appear) with mozregression, and it was a little choppy as a whole but it is hard to make a conclusion if that was causing the input freeze or not, too random to reproduce. Some bugs or problems just appear at any time for unknown reasons, and then they dissapear at any time for unknown reasons.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.