635606 - Loading a tab crashes fennec [@ nsTableFrame::DisplayGenericTablePart ]

Status: RESOLVED WORKSFORME

(Core :: Layout: Tables, defect)

Description

[(no longer active)]

Page address: http://reroad.blogspot.com/

crash report: https://crash-stats.mozilla.com/report/index/bp-00fb8a1e-5197-44bb-ad48-0a92e2110220

https://crash-stats.mozilla.com/report/index/bp-ed825c18-9fa5-4938-a888-881522110220
Happens every time I visit this web page on the latest nightly.

Comment 1

[(no longer active)]

 Forgot to mention that it is only the tab which crashes.

Comment 2

[Brad Lassey [:blassey] (use needinfo?)]

need STR to consider its blocking status

Comment 3

[Matt Brubeck (:mbrubeck)]

I can repro this just by loading http://reroad.blogspot.com/ on Android.

Comment 4

[(no longer active)]

(In reply to comment #3)
> I can repro this just by loading http://reroad.blogspot.com/ on Android.

Yes, that is the only STR one needs to reproduce.

Comment 5

[Boris Zbarsky [:bzbarsky]]

That stack in the crash report looks totally wrong...

Can anyone reproduce this in a debug build?

Comment 6

[Doug Turner (:dougt)]

no crash on g2 running a build from the trunk.

Comment 7

[Doug Turner (:dougt)]

i did notice that there are two html5 videos on that site.  on older builds, we did preload a bunch of data for each video.  wesj did fix that for the beta5.

matt, are you using the nightly?

Comment 8

[Matt Brubeck (:mbrubeck)]

I was using a local trunk build before, and reproduced the crash on G2 and on Galaxy Tab.

Today, using both the nightly and a more recent local build, I cannot reproduce the crash.

Comment 9

[Alon Zakai (:azakai)]

I cannot reproduce this on a Galaxy S with a build from yesterday. I can even play the video elements successfully.

Comment 10

[Matt Brubeck (:mbrubeck)]

Please reopen if anyone is still seeing this in the latest nightly builds.

Comment 11

[(no longer active)]

Note that I don't think that this bug was actually fixed.  It's just that the site in question is a micro-blog, and is changing frequently, so I think this is now WFM because of the markup changes on the website...