Looking for saved searches? click on "Search Bugs" above.

cairo_scaled_font_destroy: Assertion `scaled_font->ref_count > 0' failed.

RESOLVED FIXED in mozilla1.9beta1

Status

()

Core
Graphics
P2
critical
RESOLVED FIXED
10 years ago
10 years ago

People

(Reporter: reed, Assigned: karlt)

Tracking

({assertion, crash, topcrash})

Trunk
mozilla1.9beta1
x86
Linux
assertion, crash, topcrash
Points:
---
Bug Flags:
blocking1.9 +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

10 years ago
I've been continually getting shutdown crashes with the following error:
firefox-bin: /build/buildd/libcairo-1.4.10/src/cairo-scaled-font.c:617: cairo_scaled_font_destroy: Assertion `scaled_font->ref_count > 0' failed.

Breakpad IDs:
* bp-5c351700-7815-11dc-8210-001a4bd43ef6
* bp-89bef55e-7880-11dc-b8f4-001a4bd43e5c
Flags: blocking1.9?

Comment 1

10 years ago
we should probably not call cairo_debug_reset_static_data in opt builds..

Comment 2

10 years ago
Created attachment 285921 [details] [diff] [review]
fix

this should disable it in non-test builds
Assignee: nobody → pavlov
Status: NEW → ASSIGNED
Attachment #285921 - Flags: review?(vladimir)
(Assignee)

Comment 3

10 years ago
(In reply to comment #2)
> Created an attachment (id=285921) [details]
> fix
> 
> this should disable it in non-test builds
> 

I wonder if that should be disabled for system cairo too (as we'd be sharing the cairo).

To work-around this crash we may need to do the same here:

http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/gfx/thebes/src/gfxPangoFonts.cpp&rev=1.109&mark=219-221#215
(Reporter)

Comment 4

10 years ago
Comment on attachment 285921 [details] [diff] [review]
fix

This partly fixes a shutdown crash that I hit almost every day or every other day.
Attachment #285921 - Flags: approvalM9?
Attachment #285921 - Flags: approval1.9?
Comment on attachment 285921 [details] [diff] [review]
fix

a=endgame drivers for M9
Attachment #285921 - Flags: approvalM9?
Attachment #285921 - Flags: approvalM9+
Attachment #285921 - Flags: approval1.9?
Attachment #285921 - Flags: approval1.9+
Flags: blocking1.9? → blocking1.9+

Comment 6

10 years ago
checked in.
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
(Reporter)

Comment 8

10 years ago
This should be a beta blocker, imho. I think this is how to nominate?
Target Milestone: --- → mozilla1.9 M9
That'll work, Reed.  

Comment 10

10 years ago
I don't think this should block beta unless something bad is happening as a result of the crash.

That said, I don't see how we would be calling that function with that set of ifdefs given the logs from the nightly builds.
Target Milestone: mozilla1.9 M9 → mozilla1.9 M10

Comment 11

10 years ago
While I don't think it should block, if we can find a fix shortly, we should probably land it for M9.
(Assignee)

Comment 12

10 years ago
Created attachment 286600 [details] [diff] [review]
don't pango_fc_font_map_shutdown in release builds

(gtk may still be using the fontmap so I wonder whether we should not shut this down until after closing the display.)
Assignee: pavlov → mozbugz
Status: REOPENED → ASSIGNED
Attachment #286600 - Flags: review?(pavlov)

Updated

10 years ago
Attachment #286600 - Flags: review?(pavlov)
Attachment #286600 - Flags: review+
Attachment #286600 - Flags: approvalM9?

Updated

10 years ago
Priority: -- → P2
Comment on attachment 286600 [details] [diff] [review]
don't pango_fc_font_map_shutdown in release builds

a=endgame drivers for M9
Attachment #286600 - Flags: approvalM9? → approvalM9+
(Assignee)

Comment 14

10 years ago
gfxPangoFonts.cpp revision 1.110.
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago10 years ago
Resolution: --- → FIXED
(Reporter)

Updated

10 years ago
Target Milestone: mozilla1.9 M10 → mozilla1.9 M9
Reed: Since you have been seeing this crash, would you mind checking the latest nightly to see if you are still seeing it? Thanks.
Blocks: 402785
I still get this abort & crash in Linux debug builds, but not in release builds.  See bug 402785.
You need to log in before you can comment on or make changes to this bug.