Closed Bug 1325813 Opened 7 years ago Closed 1 year ago

JS-implemented (Adblock?) nsIContentPolicy can be called for fonts during TabChild::ForcePaint

Categories

(Core :: Layout, defect)

52 Branch
x86
macOS
defect

Tracking

()

RESOLVED WORKSFORME
mozilla53
Tracking Status
firefox50 --- unaffected
firefox51 --- unaffected
firefox52 --- fixed
firefox53 --- fixed

People

(Reporter: asqueella, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash, regression)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-8c5e9702-0eba-435a-9140-ef7f62161225.
=============================================================

I had a crash in 2016-12-21 Nightly caused by, I guess, Adblock's implementation of content policy being called during TabChild::ForcePaint via 

* gfxFontGroup::GetFirstValidFont calling
* gfxUserFontEntry::LoadNextSrc calling
* gfxUserFontSet::UserFontCache::GetFont calling
* FontFaceSet::UserFontSet::IsFontLoadAllowed calling
* NS_CheckContentLoadPolicy

As far as I understand it's caused by the change in bug 1279086.
More specifically, bug 1308039 added the release assert that's being hit here.
Blocks: 1308039
Version: Trunk → 52 Branch
Bug 1328423 tracks backing out bug 1308039, which should resolve this at the same time.
Depends on: 1328423
Assignee: nobody → wmccloskey
Target Milestone: --- → mozilla53
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
This isn't fixed, for example: bf9f9505-d21c-481f-9944-d22512170312

Bill, what should we do about this?
Status: RESOLVED → REOPENED
Flags: needinfo?(wmccloskey)
Resolution: FIXED → ---
Looks like we are coming from this code: <https://hg.mozilla.org/mozilla-central/annotate/3e73fd638e68/gfx/thebes/gfxTextRun.cpp#l1878>.

Jonathan, is it possible to somehow ensure that the font isn't used for painting while LoadState() returns gfxUserFontEntry::STATUS_NOT_LOADED?
Flags: needinfo?(jfkthame)
(In reply to :Ehsan Akhgari from comment #7)
> This isn't fixed, for example: bf9f9505-d21c-481f-9944-d22512170312
> 
> Bill, what should we do about this?

The buildid for that crash is 20161102030205. Someone was running a really old build. The fixes for this stuff landed in bug 1328423 (so January 2017).
Flags: needinfo?(wmccloskey)
Assignee: wmccloskey → nobody
QA Whiteboard: qa-not-actionable

Since the crash volume is low (less than 5 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.

For more information, please visit auto_nag documentation.

Severity: critical → S3

The severity field for this bug is relatively low, S3. However, the bug has 3 duplicates.
:dholbert, could you consider increasing the bug severity?

For more information, please visit auto_nag documentation.

Flags: needinfo?(dholbert)

Extensions aren't allowed to reimplement nsIContentPolicy anymore

Status: REOPENED → RESOLVED
Closed: 7 years ago1 year ago
Flags: needinfo?(jfkthame)
Flags: needinfo?(dholbert)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.