回复： Orbacus 4.1.3 memory l eak? who cares?
Zhai <[email protected]> Sat, 19 Nov 2005 17:10:48 +0800 (CST)
| Newsgroups | gmane.comp.corba.orbacus |
|---|---|
| Message-ID | <[email protected]> |
after more test, now we get the following results, it
seems memory leaks existing in OB413d.dll:
[I] Starting Purify'd
D:\zhaimingyu_view\open2000e\src\rtdbms\test_graph\Debug\test_open.exe
at 2005-11-19 16:42:14
[I] Loading Purify'd C:\WINDOWS\system32\WS2HELP.dll
at 0x00380000 (preferred 0x71a10000)
[I] Loading Purify'd
D:\users\ems\open2000e\dll\pub.dll at 0x003a0000
(preferred 0x10000000)
[I] Loading Purify'd
D:\users\ems\open2000e\dll\odb_apiall_lib.dll at
0x00450000 (preferred 0x10000000)
[I] Loading Purify'd
D:\users\ems\open2000e\dll\libsam_service.dll at
0x00b60000 (preferred 0x10000000)
[I] Loading Purify'd Purify.rsc at 0x01f10000
(preferred 0x10000000)
[I] Loading Purify'd
D:\users\ems\open2000e\STL4VC\LIB\stlport_vc645.dll at
0x10000000
[I] Loading Purify'd C:\WINDOWS\system32\MSVCRTD.dll
at 0x10200000
[I] Loading pureWQ.dll at 0x3e000000
[I] Loading PURERT.DLL at 0x3f000000
[I] Loading Purify'd C:\WINDOWS\system32\WSOCK32.dll
at 0x51a40000
[I] Loading Purify'd c:\ooc\lib\JTC201d.dll at
0x53000000
[I] Loading Purify'd c:\ooc\lib\OB413d.dll at
0x54000000
[I] Loading Purify'd C:\WINDOWS\system32\MSVCRT.dll at
0x57be0000
[I] Loading Purify'd C:\WINDOWS\system32\USER32.dll at
0x67d10000
[I] Loading Purify'd C:\WINDOWS\system32\ADVAPI32.dll
at 0x67da0000
[I] Loading Purify'd C:\WINDOWS\system32\RPCRT4.dll at
0x67e50000
[I] Loading Purify'd C:\WINDOWS\system32\GDI32.dll at
0x67ef0000
[I] Loading Purify'd C:\WINDOWS\system32\KERNEL32.dll
at 0x6c800000
[I] Loading Purify'd C:\WINDOWS\system32\NTDLL.dll at
0x6c920000
[I] Loading Purify'd C:\WINDOWS\system32\WS2_32.dll at
0x71a20000
[I] Loading Purify'd C:\WINDOWS\system32\MSVCP60.dll
at 0x75ff0000
[I] Loading C:\WINDOWS\system32\USER32.dll at
0x77d10000
[I] Loading C:\WINDOWS\system32\ADVAPI32.dll at
0x77da0000
[I] Loading C:\WINDOWS\system32\RPCRT4.dll at
0x77e50000
[I] Loading C:\WINDOWS\system32\GDI32.dll at
0x77ef0000
[I] Loading kernel32.dll at 0x7c800000
[I] Loading ntdll.dll at 0x7c920000
[I] Loading Purify'd C:\WINDOWS\system32\IMM32.DLL at
0x76300000
[I] Loading Purify'd C:\WINDOWS\system32\LPK.DLL at
0x62c20000
[I] Loading Purify'd C:\WINDOWS\system32\USP10.dll at
0x73fa0000
[I] Starting main
[W] PAR: Both Debug and non-Debug versions of CRT are
active; This may cause CRT heap operations to fail. {1
occurrence}
[I] Loading Purify'd C:\WINDOWS\system32\mswsock.dll
at 0x719c0000
[I] Loading Purify'd C:\WINDOWS\system32\hnetcfg.dll
at 0x60fd0000
[I] Searching for all memory leaks...
[I] MPK: Potential memory leak of 27 bytes from 1
block allocated in OB::Alloc(UINT,DWORD) [OB413d.dll]
Offset 0x00000008 referenced by 0x0309a400, a location
in a malloc'd block
Distribution of potentially leaked blocks
Allocation location
malloc [dbgheap.c:129]
_CRTIMP void * __cdecl malloc (
size_t nSize
)
=> {
void *res = _nh_malloc_dbg(nSize, _newmode,
_NORMAL_BLOCK, NULL, 0);
return res;
OB::Alloc(UINT,DWORD) [Basic.cpp:199]
CORBA::string_alloc(DWORD) [Basic.cpp:557]
CORBA::string_dup(char const*) [Basic.cpp:588]
OB::StrForSeq::=(char const*) [Basic.cpp:875]
OB::Properties::setProperty(char const*,char const*)
[Properties.cpp:160]
OB::ParseArgs(int&,char * *,Properties::OB
*,Logger::OB *) [ORB_init.cpp:101]
OBCORBA::ORB_init(int&,char * *,Properties::OB
*,Logger::OB *,Reactor::OB *,char const*,char const*)
[ORB_init.cpp:688]
OBCORBA::ORB_init(int&,char * *,Properties::OB *,char
const*,char const*) [ORB_init.cpp:941]
ODB::COrbMgr::InitOrb(char const*)
[D:\zhaimingyu_view\open2000e\src\rtdbms\odb_lib\src\odb_orbmgr.cpp:97]
[I] MPK: Potential memory leak of 17 bytes from 1
block allocated in OB::Alloc(UINT,DWORD) [OB413d.dll]
[I] MPK: Potential memory leak of 24 bytes from 1
block allocated in OB::Alloc(UINT,DWORD) [OB413d.dll]
[I] MPK: Potential memory leak of 30 bytes from 1
block allocated in OB::Alloc(UINT,DWORD) [OB413d.dll]
[I] MPK: Potential memory leak of 26 bytes from 1
block allocated in OB::Alloc(UINT,DWORD) [OB413d.dll]
[I] MPK: Potential memory leak of 12 bytes from 1
block allocated in OB::Alloc(UINT,DWORD) [OB413d.dll]
[I] MPK: Potential memory leak of 9 bytes from 1 block
allocated in OB::Alloc(UINT,DWORD) [OB413d.dll]
[I] MPK: Potential memory leak of 9 bytes from 1 block
allocated in OB::Alloc(UINT,DWORD) [OB413d.dll]
--- Zhai <[email protected]>写道:
> Hi,
> we run an application, a server and a client, the
> client invlkes a *.dll dynamic library. we purified
> the client and run, purify reported:
> 1.[I] Starting Purify'd
>
D:\OB-4.1.3\ob\demo\hello\clien_dll_poa\Debug\clien_dll_poa.exe
> at 2005-11-12 17:10:52
> [I] Loading Purify'd
> C:\WINDOWS\system32\MSVCIRTD.dll
> at 0x00380000 (preferred 0x102a0000)
> [I] Loading Purify'd
> C:\WINDOWS\system32\WS2HELP.dll
> at 0x003e0000 (preferred 0x71a10000)
> [I] Loading Purify'd
> C:\WINDOWS\system32\MSVCRTD.dll
> at 0x01400000 (preferred 0x10200000)
> [I] Loading Purify'd Purify.rsc at 0x028c0000
> (preferred 0x10000000)
> [I] Loading Purify'd
> D:\users\ems\open2000e\dll\hello_dll.dll at
> 0x10000000
> [I] Loading pureWQ.dll at 0x3e000000
> [I] Loading PURERT.DLL at 0x3f000000
> [I] Loading Purify'd
> C:\WINDOWS\system32\WSOCK32.dll
> at 0x51a40000
> [I] Loading Purify'd C:\WINDOWS\system32\MSVCRT.dll
> at 0x57be0000
> [I] Loading Purify'd
> C:\WINDOWS\system32\ADVAPI32.dll
> at 0x67da0000
> [I] Loading Purify'd C:\WINDOWS\system32\RPCRT4.dll
> at 0x67e50000
> [I] Loading Purify'd
> C:\WINDOWS\system32\KERNEL32.dll
> at 0x6c800000
> [I] Loading Purify'd C:\WINDOWS\system32\NTDLL.dll
> at
> 0x6c920000
> [I] Loading Purify'd C:\WINDOWS\system32\WS2_32.dll
> at 0x71a20000
> [I] Loading C:\WINDOWS\system32\ADVAPI32.dll at
> 0x77da0000
> [I] Loading C:\WINDOWS\system32\RPCRT4.dll at
> 0x77e50000
> [I] Loading kernel32.dll at 0x7c800000
> [I] Loading ntdll.dll at 0x7c920000
> [I] Starting main
> [W] PAR: Both Debug and non-Debug versions of CRT
> are
> active; This may cause CRT heap operations to fail.
> {1 occurrence}
> 2.[I] Summary of new memory leaks... {21 bytes, 1
> block}
> [I] MPK: Potential memory leak of 21 bytes from
> 1
> block allocated in main [graph_get.exe]
> Offset 0x00000008 referenced by
> 0x02eb48b0, a location in a C++ new block
> Distribution of potentially leaked
> blocks
> Allocation location
> malloc [dbgheap.c:129]
> _CRTIMP void * __cdecl malloc (
> size_t nSize
> )
> => {
> void *res =
> _nh_malloc_dbg(nSize, _newmode, _NORMAL_BLOCK, NULL,
> 0);
>
> return res;
> main
> [d:\graph_get\test_open.cpp:87]
> CODB_NET ::
> GRAPH_REAL_RSP_var lp_graph_real_rsp;
>
>
> => kk =
>
api_net.GraphGetData(graph_real_req,lp_graph_real_rsp);
> if(kk < 0)
> {
> printf("
> invoke remote rtdbms GraphGetData error\n");
> mainCRTStartup [crtexe.c:338]
> [I] Summary of new memory leaks... {0 bytes, 0
> blocks}
> 3.bytes leaks: 0+1256 to 0+122789, and etc.
>
> More, we observe the client end using "task
> manager", the two entries "memory used" and "vitural
> memory size" varies from 10536K, 50240K to 64748K,
> 112300K to 80444K, 112488K.
>
> from above, does the client leak memories?
>
>
>
>
> NOTES:
> 1. Orbacus 4.1.3, VC 6.0, STL4VC
> 2. jtcd.lib, jtc201d.dll, obd.lib, ob413d.dll,
> i.e.
> debug dynamic lib
> 3. when jtcd.lib and obd.lib are compiled,
> OLD_IOSTREAM_CURRENT is set to "no"
>
>
> Regards
>
>
>
>
>
>
>
___________________________________________________________
>
> 雅虎免费G邮箱－中国第一绝无垃圾邮件骚扰超大邮箱
> http://cn.mail.yahoo.com
>
> _______________________________________________
> OB-Users Mailing List - [email protected]
> http://mail.ooc.nf.ca/mailman/listinfo/ob-users
> Visit our support FAQ before you send a message.
> http://www.orbacus.com/faq/support.html
>
__________________________________________________
赶快注册雅虎超大容量免费邮箱?
http://cn.mail.yahoo.com
_______________________________________________
OB-Users Mailing List - [email protected]
http://mail.ooc.nf.ca/mailman/listinfo/ob-users
Visit our support FAQ before you send a message.
http://www.orbacus.com/faq/support.html