[directfb-users] still objects in ?Layer Region Pool?

[Strelchun, Timothy]

Hi Pravinkumar,

Has trouble because of following error?
Can any one guide me how do i resolved this..
(!!!) *** WARNING [still objects in ?Layer Region Pool?] *** [object.c:241 in
fusion_object_pool_destroy()] (!!!) *** WARNING [still objects in ?Layer
Context Pool?] *** [object.c:241 in fusion_object_pool_destroy()] (!!!) ***
WARNING [still objects in ?Surface Pool?] *** [object.c:241 in
fusion_object_pool_destroy()]

Normally, I have found that the above message means an interface reference was not released that was previously obtained (such as by the call pLayer->Release(pLayer); ) that should have been when shutting down prior to shutting down the super interface ( pDFB->Release(pDFB); ).

Timothy

--

Timothy Strelchun
Software Engineering
NTG Service Provider Division (formally DHG)
Intel Corporation

-----Original Message-----
Subject: [directfb-users] still objects in ?Layer Region Pool?
Content-Type: text/plain; charset="windows-1252"
Hi Every one,
Has trouble because of following error?
Can any one guide me how do i resolved this..
My system details are..
Host: Ubuntu 11.04
Target: Db-1200 board with Au-1250on board Target OS: Debian Lenny 5.0
A. binutils-2.15.tar.bz2 B. crosstool-0.43.tar.gz C. gcc-3.4.4.tar.bz2
(provided by vendor) D. glibc-2.3.2.tar.bz2 E.
glibc-linuxthreads-2.3.2.tar.bz2 F. Linux-2.6.28.tar.gz (sourse code provided
by vendor)
what this error means and have anyone work on this and have a solution..
~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.4.3 |~~~~~~~~~~~~~~~~~~~~~~~~~~ ?
2001-2009 The world wide DirectFB Open Source Community ? 2000-2004
Convergence (integrated media) GmbH ????????????????????????????????
(*) DirectFB/Core: Single Application Core. (2010-04-27 18:24)
(*) Direct/Thread: Started ?VT Switcher? (143) [CRITICAL OTHER/OTHER 0/0]
<2093056>?
(*) Direct/Thread: Started ?VT Flusher? (144) [DEFAULT OTHER/OTHER 0/0]
<2093056>?
(*) DirectFB/FBDev: Found ?AU1200? (ID 0) with frame buffer at 0?08000000,
1500k (MMIO 0?00000000, 0k)
(*) Direct/Thread: Started ?tslib Input? (145) [INPUT OTHER/OTHER 0/0]
<2093056>?
(*) DirectFB/Input: tslib touchscreen 0 0.1 (tslib)
(*) Direct/Thread: Started ?Keyboard Input? (146) [INPUT OTHER/OTHER 0/0]
<2093056>?
(*) DirectFB/Input: Keyboard 0.9 (directfb.org)
(*) DirectFB/Graphics: Generic Software Rasterizer 0.6 (directfb.org)
(*) DirectFB/Core/WM: Default 0.3 (directfb.org) (!!!) *** ONCE [no mode
found for 800?480] *** [fbdev.c:1288 in dfb_fbdev_find_mode()] (!!!) ***
WARNING [letting unprivileged IDirectFBDisplayLayer::GetSurface() call pass
until cooperative level handling is finished] ***
[idirectfbdisplaylayer.c:174 in IDirectFBDisplayLayer_GetSurface()]
(!) [ 137: 0.000] ?> Caught signal 10 (sent by the kernel) <?
(!!!) *** WARNING [still objects in ?Layer Region Pool?] *** [object.c:241 in
fusion_object_pool_destroy()] (!!!) *** WARNING [still objects in ?Layer
Context Pool?] *** [object.c:241 in fusion_object_pool_destroy()] (!!!) ***
WARNING [still objects in ?Surface Pool?] *** [object.c:241 in
fusion_object_pool_destroy()]

[Pravinkumar Chavan]

Post by Strelchun, Timothy
Hi Pravinkumar,

Has trouble because of following error?
Can any one guide me how do i resolved this..
(!!!) *** WARNING [still objects in ?Layer Region Pool?] ***

[object.c:241 in

fusion_object_pool_destroy()] (!!!) *** WARNING [still objects in ?Layer
Context Pool?] *** [object.c:241 in fusion_object_pool_destroy()] (!!!)

***

WARNING [still objects in ?Surface Pool?] *** [object.c:241 in
fusion_object_pool_destroy()]

Normally, I have found that the above message means an interface reference
was not released that was previously obtained (such as by the call
pLayer->Release(pLayer); ) that should have been when shutting down prior
to shutting down the super interface ( pDFB->Release(pDFB); ).
Timothy

Thanks Strelchun,

Actually I am newbies and really not have much knowledge of this thing.
Can you please tell me which files I need to check to see above pointers. I
will try to apply the solution you told above. Do I need to do something
from kernel side or from the application that is running on my device.
Because the while my application launches on device this error appears and
application hangs at that point.

Post by Strelchun, Timothy
--
Timothy Strelchun
Software Engineering
NTG Service Provider Division (formally DHG)
Intel Corporation

-----Original Message-----
Subject: [directfb-users] still objects in ?Layer Region Pool?
<
Content-Type: text/plain; charset="windows-1252"
Hi Every one,
Has trouble because of following error?
Can any one guide me how do i resolved this..
My system details are..
Host: Ubuntu 11.04
Target: Db-1200 board with Au-1250on board Target OS: Debian Lenny 5.0
A. binutils-2.15.tar.bz2 B. crosstool-0.43.tar.gz C. gcc-3.4.4.tar.bz2
(provided by vendor) D. glibc-2.3.2.tar.bz2 E.
glibc-linuxthreads-2.3.2.tar.bz2 F. Linux-2.6.28.tar.gz (sourse code

provided

by vendor)
what this error means and have anyone work on this and have a solution..
~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.4.3 |~~~~~~~~~~~~~~~~~~~~~~~~~~ ?
2001-2009 The world wide DirectFB Open Source Community ? 2000-2004
Convergence (integrated media) GmbH ????????????????????????????????
(*) DirectFB/Core: Single Application Core. (2010-04-27 18:24)
(*) Direct/Thread: Started ?VT Switcher? (143) [CRITICAL OTHER/OTHER 0/0]
<2093056>?
(*) Direct/Thread: Started ?VT Flusher? (144) [DEFAULT OTHER/OTHER 0/0]
<2093056>?
(*) DirectFB/FBDev: Found ?AU1200? (ID 0) with frame buffer at 0?08000000,
1500k (MMIO 0?00000000, 0k)
(*) Direct/Thread: Started ?tslib Input? (145) [INPUT OTHER/OTHER 0/0]
<2093056>?
(*) DirectFB/Input: tslib touchscreen 0 0.1 (tslib)
(*) Direct/Thread: Started ?Keyboard Input? (146) [INPUT OTHER/OTHER 0/0]
<2093056>?
(*) DirectFB/Input: Keyboard 0.9 (directfb.org)
(*) DirectFB/Graphics: Generic Software Rasterizer 0.6 (directfb.org)
(*) DirectFB/Core/WM: Default 0.3 (directfb.org) (!!!) *** ONCE [no mode
found for 800?480] *** [fbdev.c:1288 in dfb_fbdev_find_mode()] (!!!) ***
WARNING [letting unprivileged IDirectFBDisplayLayer::GetSurface() call

pass

until cooperative level handling is finished] ***
[idirectfbdisplaylayer.c:174 in IDirectFBDisplayLayer_GetSurface()]
(!) [ 137: 0.000] ?> Caught signal 10 (sent by the kernel) <?
(!!!) *** WARNING [still objects in ?Layer Region Pool?] ***

[object.c:241 in

fusion_object_pool_destroy()] (!!!) *** WARNING [still objects in ?Layer
Context Pool?] *** [object.c:241 in fusion_object_pool_destroy()] (!!!)

***

WARNING [still objects in ?Surface Pool?] *** [object.c:241 in
fusion_object_pool_destroy()]

_______________________________________________
directfb-users mailing list
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users

--
**
_________________________

Pravinkumar Chavan
Software Engineer
[phone]
En Route Media Pvt. Ltd.


**
*_________________________*
*
*

[Pravinkumar Chavan]

Post by Strelchun, Timothy
Hi Pravinkumar,

Post by Pravinkumar Chavan
Actually I am newbies and really not have much
knowledge of this thing. Can you please tell me
which files I need to check to see above
pointers. I will try to apply the solution you
told above. Do I need to do something from kernel
side or from the application that is running on
my device. Because the while my application
launches on device this error appears and
application hangs at that point.

Post by Strelchun, Timothy
Normally, I have found that the above message means
an interface reference was not released that was
previously obtained (such as by the call
pLayer->Release(pLayer); ) that should have been
when shutting down prior to shutting down the super
interface ( pDFB->Release(pDFB); ).

The interface pointer variables named pLayer and pDFB
are examples only of variables you "may" be using in
"your" application. For example, when you call the
IDirectFB::GetDisplayLayer function it returns a
pointer to an IDirectFBDisplayLayer interface for
which YOU the caller of the function now owns a
reference to (maybe in a variable named "pLayer"),
and thus you must call its Release function before
releasing the IDirectFB interface reference (which
you also own a reference to (stored in a variable
maybe named "pDFB") by calling the DirectFBCreate
function. Clearly, this only involves you application
in user mode and no kernel mode work.
Good luck!
Cheers,
Timothy
Thanks again..

"We are not using directfb library or any of its API in our Qt application.
Rather we have set QWS_DISPLAY = directfb which is to use directfb as the
driver for the framebuffer to which we are directing our Qt application
output. I think we have some problem in the directfb code. I am using
Directfb-1.4.14. May be we are not using the directfb properly."
--
**
_________________________

Pravinkumar Chavan
Software Engineer
[phone]
En Route Media Pvt. Ltd.


**
*_________________________*
*
*

[Sriram Neelakandan]

What version of Qt ?
must be a bug in Qt/DirectFB plugin then

On Wed, Feb 8, 2012 at 12:24 PM, Pravinkumar Chavan <

Post by Pravinkumar Chavan

Post by Strelchun, Timothy
Hi Pravinkumar,

Post by Pravinkumar Chavan
Actually I am newbies and really not have much
knowledge of this thing. Can you please tell me
which files I need to check to see above
pointers. I will try to apply the solution you
told above. Do I need to do something from kernel
side or from the application that is running on
my device. Because the while my application
launches on device this error appears and
application hangs at that point.

Post by Strelchun, Timothy
Normally, I have found that the above message means
an interface reference was not released that was
previously obtained (such as by the call
pLayer->Release(pLayer); ) that should have been
when shutting down prior to shutting down the super
interface ( pDFB->Release(pDFB); ).

The interface pointer variables named pLayer and pDFB
are examples only of variables you "may" be using in
"your" application. For example, when you call the
IDirectFB::GetDisplayLayer function it returns a
pointer to an IDirectFBDisplayLayer interface for
which YOU the caller of the function now owns a
reference to (maybe in a variable named "pLayer"),
and thus you must call its Release function before
releasing the IDirectFB interface reference (which
you also own a reference to (stored in a variable
maybe named "pDFB") by calling the DirectFBCreate
function. Clearly, this only involves you application
in user mode and no kernel mode work.
Good luck!
Cheers,
Timothy
Thanks again..

"We are not using directfb library or any of its API in our Qt
application. Rather we have set QWS_DISPLAY = directfb which is to use
directfb as the driver for the framebuffer to which we are directing our Qt
application output. I think we have some problem in the directfb code. I am
using Directfb-1.4.14. May be we are not using the directfb properly."
--
**
_________________________
Pravinkumar Chavan
Software Engineer
[phone]
En Route Media Pvt. Ltd.
**
*_________________________*
*
*
_______________________________________________
directfb-users mailing list
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users

[Pravinkumar Chavan]

Post by Sriram Neelakandan
On Wed, Feb 8, 2012 at 12:24 PM, Pravinkumar Chavan <

Post by Pravinkumar Chavan

Post by Strelchun, Timothy
Hi Pravinkumar,

Post by Pravinkumar Chavan
Actually I am newbies and really not have much
knowledge of this thing. Can you please tell me
which files I need to check to see above
pointers. I will try to apply the solution you
told above. Do I need to do something from kernel
side or from the application that is running on
my device. Because the while my application
launches on device this error appears and
application hangs at that point.

Post by Strelchun, Timothy
Normally, I have found that the above message means
an interface reference was not released that was
previously obtained (such as by the call
pLayer->Release(pLayer); ) that should have been
when shutting down prior to shutting down the super
interface ( pDFB->Release(pDFB); ).

The interface pointer variables named pLayer and pDFB
are examples only of variables you "may" be using in
"your" application. For example, when you call the
IDirectFB::GetDisplayLayer function it returns a
pointer to an IDirectFBDisplayLayer interface for
which YOU the caller of the function now owns a
reference to (maybe in a variable named "pLayer"),
and thus you must call its Release function before
releasing the IDirectFB interface reference (which
you also own a reference to (stored in a variable
maybe named "pDFB") by calling the DirectFBCreate
function. Clearly, this only involves you application
in user mode and no kernel mode work.
Good luck!
Cheers,
Timothy
Thanks again..

"We are not using directfb library or any of its API in our Qt
application. Rather we have set QWS_DISPLAY = directfb which is to use
directfb as the driver for the framebuffer to which we are directing our Qt
application output. I think we have some problem in the directfb code. I am
using Directfb-1.4.14. May be we are not using the directfb properly."
What version of Qt ? must be a bug in Qt/DirectFB plugin then

The Qt version is 4.6.2
I am not sure, if there is a bug in Qt/DirectFB plugin...
Can you please explain in brief so that i will do some check about it..
--

Post by Sriram Neelakandan

Post by Pravinkumar Chavan
_________________________
Pravinkumar Chavan
Software Engineer
[phone]
En Route Media Pvt. Ltd.
*_________________________*
*
*
_______________________________________________
directfb-users mailing list
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users

--
Sriram Neelakandan
Author - Embedded Linux System Design And Development (
http://tinyurl.com/2doosu)

--
**
_________________________

Pravinkumar Chavan
Software Engineer
[phone]
En Route Media Pvt. Ltd.


**
*_________________________*
*
*