I have a suggestion that might help on getting the problem to show up more
quickly and with less windows/tabs:
After starting up the gdb/firefox combo, start up a 2nd firefox (I use firefox
--class=mysecondprofile) and have it load anther session with plenty of
tabs/windows. Start a 3d, 4th, ... fox as well if you like.
When I do this, each of the foxes need not have so many windows and tabs before
the Untitled windows start popping up.
This method rhymes with your working assumption about the bug being related to
X interactions: having multiple foxes creates more competition for getting the
attention of X, and competition for X resources will cause unpredictable delays
in creating windows etc.
Also, this way, the size of the gdb/fox combo may also be more manageable.
Robert Bradbury,
I have a suggestion that might help on getting the problem to show up more
quickly and with less windows/tabs:
After starting up the gdb/firefox combo, start up a 2nd firefox (I use firefox mysecondprofile ) and have it load anther session with plenty of
--class=
tabs/windows. Start a 3d, 4th, ... fox as well if you like.
When I do this, each of the foxes need not have so many windows and tabs before
the Untitled windows start popping up.
This method rhymes with your working assumption about the bug being related to
X interactions: having multiple foxes creates more competition for getting the
attention of X, and competition for X resources will cause unpredictable delays
in creating windows etc.
Also, this way, the size of the gdb/fox combo may also be more manageable.