Bug 81709

Summary: Win32 printer backend fails with scaled_font->cache_frozen assertion
Product: cairo Reporter: rodrigo <rodrigorivascosta>
Component: win32 backendAssignee: cairo-bugs mailing list <cairo-bugs>
Status: RESOLVED FIXED QA Contact: cairo-bugs mailing list <cairo-bugs>
Severity: normal    
Priority: medium    
Version: 1.12.16   
Hardware: x86 (IA32)   
OS: Windows (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: PATCH: fix the cache_frozen assertion

Description rodrigo 2014-07-24 08:51:54 UTC 
Created attachment 103393 [details]
PATCH: fix the cache_frozen assertion

Hello all!

I'm trying to use cairo 1.12.16 to print on a Win32 printer, and I'm always getting an assertion error:

    At cairo-scaled-font.c:2961:
    Assertion failed: "scaled_font->cache_frozen"

Googling around, I found a message in the mailing list from Dec. 2013 [1] with this very same error and some suggestions. Unfortunately it seemed to have passed unnoticed...

Anyway, I've written a patch that seems to fix the issue (attached).

Best regards.

 [1]: http://lists.cairographics.org/archives/cairo/2013-December/024848.html
Comment 1 Adrian Johnson 2014-08-18 13:59:36 UTC 
I've tested this patch and it works for me. Do you want to provide your full name for the commit or just "rodrigo <rodrigorivascosta@gmail.com>"?
Comment 2 rodrigo 2014-08-18 14:14:11 UTC 
(In reply to comment #1)
> I've tested this patch and it works for me. Do you want to provide your full
> name for the commit or just "rodrigo <rodrigorivascosta@gmail.com>"?

"rodrigo" is my bugzilla user. My full name is "Rodrigo Rivas Costa", that will be cool.

Thanks!
Comment 3 Adrian Johnson 2014-08-18 14:44:12 UTC 
commit 932548ef25864958ef966ffe83e7c945c3ff3cd4
Author: Rodrigo Rivas Costa <rodrigorivascosta@gmail.com>
Date:   Tue Aug 19 00:09:50 2014 +0930

    win32 print: fix cache_frozen assertions
    
    Bug 81709

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.