[maemo-developers] N900: Mapper, device deadlocks and clutter/GL errors

From: Alberto Mardegan mardy at users.sourceforge.net
Date: Thu Mar 11 12:29:20 EET 2010
Eero Tamminen wrote:
>> - Always: when I'm drawing on a texture (either loading a map tile, or 
>> using cairo on a texture) and a Hildon banner/notification appears 
>> (either from Mapper itself, or even an incoming chat notification), 
>> the texture is corrupted, and it will contain a small rectangle with 
>> pseudorandom pixels.
> 
> And the graphics being drawn when the SGX HW reset happened can be
> corrupted (as the operation was interrupted and state before the reset
> isn't recoverable).

This is a bit different: in these cases I rarely see any lines from SGX in the 
syslog. From there, everything appears fine, but the textures are corrupted.

> Note that on most(?) devices it doesn't seem to happen at all, at least
> with the pre-installed software.
> 
> But e.g. the 3rd party Maep application seems to make triggering of this
> issue (at least on some devices) easier, especially as/when it's doing
> window updates even when it's not visible (which is a clear use-time
> and resource usage bug in Maep).

In my case, I'm sure I've seen it when I was actively using the device. But now 
that I think of it, in all cases when I saw it I had a dialog on top of the 
clutter stage: the "download route" dialog, which also causes some network 
traffic to retrieve the route and then some CPU activity to parse it into a path 
and draw it on the stage, via the cairo functions.

It is quite possible that drawing happened while the clutter stage was covered 
by a dialog.

Ciao,
   Alberto

-- 
http://www.mardy.it <-- geek in un lingua international!
More information about the maemo-developers mailing list