367990 - While starting Firefox/SeaMonkey, "cairo_win32_scaled_font_select_font:SelectObject: Invalid descriptor"

Status: RESOLVED DUPLICATE of bug 367618

(Core :: Graphics, defect)

Description

[Serge Gautherie (:sgautherie)]

Today, I replaced my old video card with a brand new one.
W2K detects it, but has no driver for it (= not installed yet).
Then, it runs as 640*480 or 800*600 pixels, in 16 colors only.


[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.9) Gecko/20061211 SeaMonkey/1.0.7] (release) (W2Ksp4)
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.2pre) Gecko/20070123 SeaMonkey/1.1] (nightly) (W2Ksp4)

No bug: (before cairo)
{ (DOS console)
Document about: loaded successfully
}


[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a2pre) Gecko/20070123 SeaMonkey/1.5a] (nightly) (W2Ksp4)

(using cairo)
During splash screen,
Hang with 50% of dual cpu (= 100% of single cpu)

{ (DOS console)
cairo_win32_surface_create(bad BITSPIXEL): Opération réussie.
cairo_win32_surface_create(bad BITSPIXEL): Opération réussie.
### ERROR - unable to create search "file".
cairo_win32_surface_create(bad BITSPIXEL): Opération réussie.
cairo_win32_scaled_font_select_font:SelectObject: Descripteur non valide
}
(== succeeded/succeeded/error/succeeded/invalid)

Need to kill the process.


<firefox-3.0a2pre.en-US.win32.zip> (2007-01-23-04)

Same bug, but not getting the "ERROR" line.

Comment 1

[Serge Gautherie (:sgautherie)]

That was
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a2pre) Gecko/2007012304 Minefield/3.0a2pre] (nightly) (W2Ksp4)


[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a2pre) Gecko/20070123 SeaMonkey/1.5a] (nightly) (W2Ksp4)

Then, with graphic card driver installed, (800*600 or 1152*864):
*16 bits: works fine, as previous card did.
*256 colors: no more hang, but the browser window is almost "blank", unusable.


*****

I filed bug 368002 on the "ERROR" line.

Comment 2

[Serge Gautherie (:sgautherie)]

Same "almost blank" window with old card and driver.

Are there known issues for cairo with 8 bits color mode ?

Comment 3

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

I don't know whether we'll be supporting 4-bit or 8-bit color with 1.9; it's still undecided.  However, we should at the very least need to check for this and put up an appropriate error instead of crashing.

Comment 4

[Serge Gautherie (:sgautherie)]

(In reply to comment #1)
> *256 colors: no more hang, but the browser window is almost "blank", unusable.

(In reply to comment #2)
> Same "almost blank" window with old card and driver.
> 
> Are there known issues for cairo with 8 bits color mode ?

That "blank" issue/part is bug 367618.

Comment 5

[Serge Gautherie (:sgautherie)]

(In reply to comment #4)
> That "blank" issue/part is bug 367618.

That bug fixed the 8bits/256colors case,

and removed the error code:
{{
-	else {
-	    _cairo_win32_print_gdi_error("cairo_win32_surface_create(bad BITSPIXEL)");
-	    return _cairo_surface_create_in_error (_cairo_error (CAIRO_STATUS_INVALID_FORMAT));
-	}
}}

"I" would have to check what the behavior of the 4bits/16colors case is now...

Comment 6

[Serge Gautherie (:sgautherie)]

(In reply to comment #5)
> "I" would have to check what the behavior of the 4bits/16colors case is now...

[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9b3pre) Gecko/2008013002 SeaMonkey/2.0a1pre] (nightly) (W2Ksp4)

I restarted Windows in Safe Mode, to test 4bits/16colors:
fixed too :-)