Closed
Bug 312784
Opened 19 years ago
Closed 19 years ago
crash setting display:none on grid rows [@ nsGrid::GetPrefRowHeight]
Categories
(Core :: XUL, defect, P1)
Tracking
()
VERIFIED
FIXED
mozilla1.8rc1
People
(Reporter: frenchfrog, Assigned: bzbarsky)
References
Details
(4 keywords, Whiteboard: [sg:fix] memory corruption, fixed by 313173)
Crash Data
Attachments
(1 file, 1 obsolete file)
473 bytes,
application/vnd.mozilla.xul+xml
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051017 Firefox/1.4.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051017 Firefox/1.4.1
Firefox crash on about:config when changing a giving boolean with gmail notifier
0.5.2.1 (TB 10782990)
Reproducible: Always
Steps to Reproduce:
1.Install Gmail Notifier 0.5.2.1
(http://ftp.mozilla.org/pub/mozilla.org/extensions/gmail_notifier/gmail_notifier-0.5.2.1-fx+mz.xpi)
2.Restart Firefox to finish the installation
3.Log in your gmail account (using the icon on the status bar)
4.Put the mouse over the icon to get the tooltip
5.Open a new tab with about:config
6.Put 'gm' in the filter
7.Quick double click a couple of times on 'gm-notifier.ui.folderview' to switch
it from true to false, to false to true, it should crash after 2-3 times
Reporter | ||
Updated•19 years ago
|
Version: Trunk → 1.8 Branch
Reporter | ||
Updated•19 years ago
|
Flags: blocking1.8rc1?
Comment 1•19 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051016
Firefox/1.6a1 ID:2005101619
TB10793385Q - I could only reproduce this once, but it appears that your stack
and my stack are different.
Keywords: talkbackid
Comment 2•19 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051017
Firefox/1.4.1 ID:2005101723
It crashes but I see no talkback, only MS. Tried it on two computers with the
same result.
Once I have clicked on gm-notifier.ui.folderview, whether or not it crashes, the
process firefox.exe stays in the taskmanager after closing Firefox.
Reporter | ||
Comment 3•19 years ago
|
||
reply to comment #1, probably because it's done on different branch (I tested
the 1.8 branch and you tested the trunk)
Comment 4•19 years ago
|
||
I only see a single talkback report with this crash in talkback. If this were a
top crasher we'd consider it but this late in the game we aren't holding up the
release for non criticial top crashes.
Flags: blocking1.8rc1? → blocking1.8rc1-
Comment 5•19 years ago
|
||
TB10782990 looks like nonsense skidmarks to me: it doesn't make sense that SVG
code would be called, and one of the functions on the stack is a leaf function.
So it's not surprising that mscott can't find other crashes with the same
signature. That happens sometimes with some types of crashes; I don't know the
details about why it happens.
TB10793385Q looks more likely to have something to do with this crash.
TB10793385Q has a random address at the top, followed by
nsGrid::GetPrefRowHeight. This is more plausible -- about:config does use a
listbox and I've seen many listbox-related crashes in nsGrid functions.
Unfortunately, the random-address-at-the-top makes it hard to determine the
number of matching crashes (because of bug 304768 / bug 304769) to tell whether
this is a topcrash.
This crash might be exploitable by web content to execute arbitrary code. The
crash seems to have more to do with <listbox>, which can be used by web content,
than the chrome parts of about:config.
If this crash is a regression, a regression range would be useful.
Flags: blocking1.8rc1- → blocking1.8rc1?
Keywords: crash
Summary: crash with nsSVGCairoPathGeometry::Render on about:config → crash on about:config [@ nsGrid::GetPrefRowHeight]
Reporter | ||
Comment 6•19 years ago
|
||
Nope it's not a regression it crash way back to 1.0 (I must have a gift to fall
on bug like this)
Error message given when crashing with Firefox 1.0 and 1.0.7 (no talkback)
Microsoft Visual C++ Runtion Library
Program: C:\PROGRA~1\MOZILL~1\firefox.exe
Firefox 1.0.7
R6025
- pure virtual call
Reporter | ||
Comment 7•19 years ago
|
||
Tested Mozilla Suite 1.6, 1.7 and they crash.
Reporter | ||
Comment 8•19 years ago
|
||
sry for bugspam:
Microsoft not so usefull explanation of R6025
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html/R6025.asp
I read a couple of forum post of people having the R6025 problem (found by a
search on google) and one on them was saying that running a vc6 debug build was
suppose to assert instead of crashing. Worth a try on 1.0.7 ?
Comment 9•19 years ago
|
||
Any chance this was fixed over at bug 311710 ? If not, BZ, can you look into this?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 10•19 years ago
|
||
The fix for bug 311710 was checked in on Oct 16, and this bug was reported with
Oct 17 builds (but is not a recent regression). So the fix for bug 311710
didn't fix (or cause) this bug.
![]() |
Assignee | |
Comment 11•19 years ago
|
||
So what's going on here is that the whole grid row group is getting
display:none. We simply have no provisions for this -- we notify the parent's
layout manager that it went away, but that's nsBoxLayout and does nothing with
the notification. So now we have dangling pointers to deleted row frames in
nsGrid, and when we try to mess with them we crash.
I don't really understand what this code is doing, so I have no idea how to fix
it, much less fix safely. :(
Assignee: win32 → nobody
Component: GFX: Win32 → XP Toolkit/Widgets: XUL
QA Contact: ian → xptoolkit.xul
Version: 1.8 Branch → Trunk
Comment 12•19 years ago
|
||
(In reply to comment #5)
>about:config does use a listbox
It does? That's news to me...
(In reply to comment #11)
>So what's going on here is that the whole grid row group is getting display:none.
Um... which grid row group?
>I don't really understand what this code is doing
Join the crew ;-)
![]() |
Assignee | |
Comment 13•19 years ago
|
||
> Um... which grid row group?
There's a grid row group in the overlay which this extension installs. Then it
has a pref observer for the pref we're toggling which does, when notified of a
pref change (gm-notifier.js):
case gGMailNotifier.wm_prefs.PREF_USE_FOLDERVIEW:
var showFolders =
gGMailNotifier.wm_prefs.getBoolPref(gGMailNotifier.wm_prefs.PREF_USE_FOLDERVIEW);
document.getElementById("gm-tooltip-row").hidden = !showFolders;
where the thing with gm-tooltip-row as the ID is found in gm-core-overlay.xul;
the relevant part looks like:
<grid id="gm-notifier-tooltip-labels" hidden="true"
style="font-size:0.8em; padding:5px;">
<columns>
<column/>
<column/>
</columns>
<rows id="gm-tooltip-row">
</rows>
</grid>
I'll attach a minimal testcase that doesn't need this extension at all.
Summary: crash on about:config [@ nsGrid::GetPrefRowHeight] → crash setting display:none on grid rows [@ nsGrid::GetPrefRowHeight]
![]() |
Assignee | |
Comment 14•19 years ago
|
||
This has a slightly different stack, but I think it's the same issue.
![]() |
Assignee | |
Comment 15•19 years ago
|
||
Attachment #200209 -
Attachment is obsolete: true
Comment 16•19 years ago
|
||
not a topcrasher and it doesn't look like anyone's suggested it's exploitable
and we're already shipping this bug so not going to block on it.
Flags: blocking1.8rc1? → blocking1.8rc1-
Comment 17•19 years ago
|
||
neil and bz, sorry for the incorrect comment. about:config is a tree, not a
listbox.
Asa, I think this is exploitable and we can't easily tell whether this is a
topcrash. See comment 5.
Flags: blocking1.8rc1- → blocking1.8rc1?
![]() |
Assignee | |
Comment 18•19 years ago
|
||
> and it doesn't look like anyone's suggested it's exploitable
Dangling pointers (see comment 11) mean this is most likely exploitable.
Updated•19 years ago
|
Group: security
![]() |
Assignee | |
Updated•19 years ago
|
Assignee: nobody → bzbarsky
Priority: -- → P1
Target Milestone: --- → mozilla1.8rc1
![]() |
Assignee | |
Comment 19•19 years ago
|
||
Fixed by checkin for bug 313173
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 20•19 years ago
|
||
WFM with the Mac build from
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2005-10-21-15-trunk/. I
was able to reproduce this crash in a build from yesterday (before the patch
went in). I'm not sure I should mark this bug as verified, because François
originally reported this bug on Windows.
Comment 21•19 years ago
|
||
Assuming bug 313173 comment 17, "Fixed on branch.", applies to this bug too.
Flags: blocking1.8rc1?
Keywords: fixed1.8
![]() |
Assignee | |
Comment 22•19 years ago
|
||
Er... yes, it does. Thanks, Jesse!
Reporter | ||
Updated•19 years ago
|
Status: RESOLVED → VERIFIED
Updated•19 years ago
|
Flags: blocking1.8rc1+
Flags: blocking1.7.13?
Flags: blocking-aviary1.0.8?
Whiteboard: [sg:fix] memory corruption
Updated•19 years ago
|
Flags: blocking1.7.13?
Flags: blocking1.7.13+
Flags: blocking-aviary1.0.8?
Flags: blocking-aviary1.0.8+
Updated•19 years ago
|
Flags: testcase+
Updated•19 years ago
|
Whiteboard: [sg:fix] memory corruption → [sg:fix] memory corruption fixed by 313173
Updated•19 years ago
|
Whiteboard: [sg:fix] memory corruption fixed by 313173 → [sg:fix] memory corruption, fixed by 313173
![]() |
Assignee | |
Comment 24•19 years ago
|
||
Fixed on branches by checkin of bug 313173
Keywords: fixed-aviary1.0.8,
fixed1.7.13
Comment 25•19 years ago
|
||
v.fixed on 1.0.8 Aviary with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20060209 Firefox/1.0.7
Keywords: fixed-aviary1.0.8 → verified-aviary1.0.8
Updated•19 years ago
|
Group: security
Updated•18 years ago
|
Flags: in-testsuite+ → in-testsuite?
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: xptoolkit.xul → xptoolkit.widgets
Comment 26•16 years ago
|
||
crash test landed
http://hg.mozilla.org/mozilla-central/rev/2057466b414a
Flags: in-testsuite? → in-testsuite+
Updated•14 years ago
|
Crash Signature: [@ nsGrid::GetPrefRowHeight]
You need to log in
before you can comment on or make changes to this bug.
Description
•