Trolltech Home | Qt-solutions Home | Recent Threads | All Threads | Author | Date
All threads index page 1

Qt-solutions Archive, October 2007
QT 4 is not releasing memory ???


Message 1 in thread

Hi

I am just getting started with qt4. I have tried to build the
"Analog Clock" example from the QT site, and when I run  valgrind on it,
I get the following result:

==6489== IN SUMMARY: 14 errors from 8 contexts (suppressed: 81 from 1)
==6489==
==6489== malloc/free: in use at exit: 66,847 bytes in 2,236 blocks.
==6489== malloc/free: 33,721 allocs, 31,485 frees, 7,261,430 bytes
allocated.
==6489==
==6489== searching for pointers to 2,236 not-freed blocks.
==6489== checked 523,024 bytes.

LEAK SUMMARY:
==6489==    definitely lost: 374 bytes in 8 blocks.
==6489==      possibly lost: 744 bytes in 3 blocks.
==6489==    still reachable: 65,729 bytes in 2,225 blocks.
==6489==         suppressed: 0 bytes in 0 blocks.

Is there a problem in the QT environment ?

System info:

valgrind-3.2.1-Debian
qt-4.2.3
Linux version 2.6.20-16-generic (root@terranova)
(gcc version 4.1.2(Ubuntu 4.1.2-0ubuntu4))

Rgards, Kim S

--
 [ signature omitted ] 

Message 2 in thread

System info:

valgrind-3.2.1-Debian
qt-4.2.3
Linux version 2.6.20-16-generic
(gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4))

If you need more info please let me know ?



PRIYAN *OB* wrote:
> please specify your system configuration...I
>
> On 10/9/07, *Kim S* <ks@xxxxxxxxxxx <mailto:ks@xxxxxxxxxxx>> wrote:
>
>     Hi
>
>     I am just getting started with qt4. I have tried to build the
>     "Analog Clock" example from the QT site, and when I run  valgrind
>     on it,
>     I get the following result:
>
>     ==6489== IN SUMMARY: 14 errors from 8 contexts (suppressed: 81 from 1)
>     ==6489==
>     ==6489== malloc/free: in use at exit: 66,847 bytes in 2,236 blocks.
>     ==6489== malloc/free: 33,721 allocs, 31,485 frees, 7,261,430 bytes
>     allocated.
>     ==6489==
>     ==6489== searching for pointers to 2,236 not-freed blocks.
>     ==6489== checked 523,024 bytes.
>
>     LEAK SUMMARY:
>     ==6489==    definitely lost: 374 bytes in 8 blocks.
>     ==6489==      possibly lost: 744 bytes in 3 blocks.
>     ==6489==    still reachable: 65,729 bytes in 2,225 blocks.
>     ==6489==         suppressed: 0 bytes in 0 blocks.
>
>     Is there a problem in the QT environment ?
>
>     System info:
>
>     valgrind-3.2.1-Debian
>     qt-4.2.3
>     Linux version 2.6.20-16-generic (root@terranova)
>     (gcc version 4.1.2(Ubuntu 4.1.2-0ubuntu4))
>
>     Rgards, Kim S
>
>     --
>     To unsubscribe - send "unsubscribe" in the subject to
>     qt-solutions-request@xxxxxxxxxxxxx
>     <mailto:qt-solutions-request@xxxxxxxxxxxxx>
>
>


--
 [ signature omitted ] 

Message 3 in thread

You may wish to post this question to qt-interest forum. It's a little 
more commonly watched.

Kim S wrote:
> System info:
> 
> valgrind-3.2.1-Debian
> qt-4.2.3
> Linux version 2.6.20-16-generic
> (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4))
> 
> If you need more info please let me know ?
> 
> 
> 
> PRIYAN *OB* wrote:
>> please specify your system configuration...I
>>
>> On 10/9/07, *Kim S* <ks@xxxxxxxxxxx <mailto:ks@xxxxxxxxxxx>> wrote:
>>
>>     Hi
>>
>>     I am just getting started with qt4. I have tried to build the
>>     "Analog Clock" example from the QT site, and when I run  valgrind
>>     on it,
>>     I get the following result:
>>
>>     ==6489== IN SUMMARY: 14 errors from 8 contexts (suppressed: 81 
>> from 1)
>>     ==6489==
>>     ==6489== malloc/free: in use at exit: 66,847 bytes in 2,236 blocks.
>>     ==6489== malloc/free: 33,721 allocs, 31,485 frees, 7,261,430 bytes
>>     allocated.
>>     ==6489==
>>     ==6489== searching for pointers to 2,236 not-freed blocks.
>>     ==6489== checked 523,024 bytes.
>>
>>     LEAK SUMMARY:
>>     ==6489==    definitely lost: 374 bytes in 8 blocks.
>>     ==6489==      possibly lost: 744 bytes in 3 blocks.
>>     ==6489==    still reachable: 65,729 bytes in 2,225 blocks.
>>     ==6489==         suppressed: 0 bytes in 0 blocks.
>>
>>     Is there a problem in the QT environment ?
>>
>>     System info:
>>
>>     valgrind-3.2.1-Debian
>>     qt-4.2.3
>>     Linux version 2.6.20-16-generic (root@terranova)
>>     (gcc version 4.1.2(Ubuntu 4.1.2-0ubuntu4))
>>
>>     Rgards, Kim S
>>
>>     --
>>     To unsubscribe - send "unsubscribe" in the subject to
>>     qt-solutions-request@xxxxxxxxxxxxx
>>     <mailto:qt-solutions-request@xxxxxxxxxxxxx>
>>
>>
> 
> 

--
 [ signature omitted ] 

Message 4 in thread

This list is for the QT Solutions package, not QT itself.

Scott

> -----Original Message-----
> From: Kim S [mailto:ks@xxxxxxxxxxx]
> Sent: Tuesday, October 09, 2007 1:32 AM
> To: qt-solutions@xxxxxxxxxxxxx
> Subject: QT 4 is not releasing memory ???
> 
> Hi
> 
> I am just getting started with qt4. I have tried to build the
> "Analog Clock" example from the QT site, and when I run  valgrind on
it,
> I get the following result:
> 
> ==6489== IN SUMMARY: 14 errors from 8 contexts (suppressed: 81 from 1)
> ==6489==
> ==6489== malloc/free: in use at exit: 66,847 bytes in 2,236 blocks.
> ==6489== malloc/free: 33,721 allocs, 31,485 frees, 7,261,430 bytes
> allocated.
> ==6489==
> ==6489== searching for pointers to 2,236 not-freed blocks.
> ==6489== checked 523,024 bytes.
> 
> LEAK SUMMARY:
> ==6489==    definitely lost: 374 bytes in 8 blocks.
> ==6489==      possibly lost: 744 bytes in 3 blocks.
> ==6489==    still reachable: 65,729 bytes in 2,225 blocks.
> ==6489==         suppressed: 0 bytes in 0 blocks.
> 
> Is there a problem in the QT environment ?
> 
> System info:
> 
> valgrind-3.2.1-Debian
> qt-4.2.3
> Linux version 2.6.20-16-generic (root@terranova)
> (gcc version 4.1.2(Ubuntu 4.1.2-0ubuntu4))
> 
> Rgards, Kim S
> 
> --
> To unsubscribe - send "unsubscribe" in the subject to qt-solutions-
> request@xxxxxxxxxxxxx

--
 [ signature omitted ]