On Sun, Jul 06, 2008 at 12:42:01PM +0200, Andreas Barth wrote:
> Hi,
> 
> * Mike Hommey ([EMAIL PROTECTED]) [080706 10:41]:
> > On Fri, Jun 20, 2008 at 11:28:05AM +0200, Alexander Sack <[EMAIL 
> > PROTECTED]> wrote:
> > > On Fri, Jun 20, 2008 at 01:07:09AM +0200, Mike Hommey wrote:
> > > > On Fri, Jun 20, 2008 at 12:43:04AM +0200, Mike Hommey wrote:
> > > > > On Fri, Jun 20, 2008 at 12:38:52AM +0200, Mike Hommey wrote:
> > > > > > On Wed, Jun 18, 2008 at 12:48:42AM +0200, Josselin Mouette wrote:
> > > > > > > Le mercredi 18 juin 2008 à 00:18 +0200, Mazen NEIFER a écrit :
> > > > > > > > Browse
> > > > > > > > http://aljazeera.net/NR/exeres/8BAC4176-2B16-450F-B8DA-7127702A17AF.htm
> > > > > > > >  and try to increase font size and it will crash.
> > > > > > > 
> > > > > > > This is indeed reproducible. Interestingly enough, a very similar 
> > > > > > > bug
> > > > > > > happens in devhelp when trying to increase the font size.
> > > > > > > 
> > > > > > > I???m attaching a full backtrace with debugging symbols.
> > > > > > 
> > > > > > Interestingly, while I can reproduce with epiphany, I can't with
> > > > > > iceweasel. Some values of the zoom factor may be triggering this
> > > > > > issue...
> > > > > 
> > > > > FWIW, iceweasel is setting zoom factor to 1.1, 1.2, 1.3, ...
> > > > 
> > > > I tried some less intriguing values for zoom factors in epiphany, and it
> > > > didn't change anything. It still crashes.
> > > > 
> > > 
> > > We had this "zoom" crash here _before_ respinning epiphany-browser on
> > > top of the final xulrunner .... Are you sure its a fresh build?
> > 
> > I build it myself yesterday. Though not against final xulrunner, but rc2,
> > which is the same.
> 
> Any news on this bug? Does it still happen? How bad is it, should it
> block testing migration?

It still happens reliably for me with the given url, though it doesn't
happen with other urls. So I would say it is not /that/ bad.

Mike



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to