The transition from nightly to aurora usually breaks a lot of tests (devs creates tests that depends on things that are only enabled on nightly). They don't release it until all tests are working and passing.
The new Aurora version is usually released on the Friday after the merge date, so apparently things are more buggy this time.
avada wrote:Middle clicking a link to open a new tab is just unbearably slow. It hangs the GUI for 3-5 seconds... WTF did they screw up now?
I can't reproduce that.
Try with with multiple content processes.
It looks like it happens every time a new tab is opened no matter how. When I open one via ctrl+t and start typing the GUI hangs after 2-3 characters for several seconds.
Update: it doesn't happen when I press ctrl+shift+a to open the addons manager. So it looks like something goes wrong on new process creation.
avada wrote:
Update: it doesn't happen when I press ctrl+shift+a to open the addons manager. So it looks like something goes wrong on new process creation.
avada wrote:
Update: it doesn't happen when I press ctrl+shift+a to open the addons manager. So it looks like something goes wrong on new process creation.
Okay, so I experience this even in save mode. With 2 or more content processes. Also even with one content process it's noticeable that firefox starts up slower, obviously because the creation of that single content process is just as slow. So I don't know how people aren't seeing this...
I'm going to hazard a guess here and say you have 'too many' content processes with the dom.ipc.processCount set to '44' in your case.
A new Profile likely only has '1' in that value, and it was recently bumped to '2' for testing. Setting it to '44' this early is totally untested, and likely never will be able to handle that many.
EDIT: It's no issue in a new profile because the default is '1'. Also a 'crap-load' of addons.
I would like to see a screen shot of your taskmanager to see if there are really 44 processes running.
TheVisitor wrote:
I'm going to hazard a guess here and say you have 'too many' content processes with the dom.ipc.processCount set to '44' in your case.
A new Profile likely only has '1' in that value, and it was recently bumped to '2' for testing. Setting it to '44' this early is totally untested, and likely never will be able to handle that many.
EDIT: It's no issue in a new profile because the default is '1'. Also a 'crap-load' of addons.
I would like to see a screen shot of your taskmanager to see if there are really 44 processes running.
As I said it only broke on the 19th before it was good. So no that's not the issue.
Also it doesn't work that way. 44 processes are only opened when I have ~44 tabs. (I also said that it happens with 1-2 content processes...)
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same.
