Comment 21 for bug 286366

On Sun, 2008-11-02 at 21:29 +0000, Alexander Sack wrote:
> hey, we try to track down a bug here and not start fundamental debats.

I'm not trying to start any debates, just tell you what problems I have
with the process of trying to find this bug. The bottom line is that it
takes a while for FF3 to trigger this problem and I cannot use FF3
without having all of the tabs that tabmix plus restores for me. If I
don't have the tabs restored (and saved before a crash) FF3 is useless
to me and I am completely unproductive.

To use the ever useful car analogy it's like asking me to drive my car
for a while without the steering wheel so that we can determine if the
steering wheel is causing the problem with the brakes.

> just do what i say for testing.

But what I'm saying is that I cannot use FF3 for the hours that it would
take to see this reproduce without the tabs that tabmix plus will
restore for me when I start using FF3.

BTW: did you notice the update to the upstream bug
(https://bugzilla.mozilla.org/show_bug.cgi?id=460916) by another seeing
the same problem with a crash-stats.mozilla.com link included?