search for: libumem

...s with the application growth of memory due to Size growth of Dictionary Objects (Like Maps) and Memory Leak. (Dictionary Objects we can print the size but its live production site where the problem is happening also there are many such object used the application) When I used Dtrace and libumem ( with mdb )to detect memory leak for C++ code. When I tried to run dtrace script available in SUN Site it stops abruptly With following error # dtrace -s ./CCagg_1.d `pgrep scadadbproc` | c++filt >> scadadbproc_dtrace dtrace: 91102 drops on CPU 0 dtrace: processing aborted: Abort du...

Hi. I''m happy to inform that the ZFS file system is now part of the FreeBSD operating system. ZFS is available in the HEAD branch and will be available in FreeBSD 7.0-RELEASE as an experimental feature. Commit log: Please welcome ZFS - The last word in file systems. ZFS file system was ported from OpenSolaris operating system. The code in under CDDL license. I''d

Boy am I a dummy. I want to simply dump out unfreed allocations when I terminate the script. What''s the secret sauce? #!/usr/sbin/dtrace -s pid$1::MyAlloc:return { bufs[arg1] = walltimestamp; } pid$1::MyFree:entry /bufs[arg0]/ { bufs[arg0] = 0; } This message posted from opensolaris.org

Howdy, I am attempting to isolate the location of a memory leak in a 4GL program, and have hit a bit of a snag. When I LD_PRELOAD libumem and run the application server, "::findleaks -fdv" reports numerous leaks: CACHE LEAKED BUFCTL CALLER 0000000100b49068 15 0000000100ef2d50 fdcon+0x6c4 0000000100b50028 1 0000000100b72ac0 fdcon+0x6c4 0000000100b49068 2 0000000100cdfb30 fdcon+0x6c4 0...

...QAContact: hua.tang at sun.com CC: zfs-crypto-discuss at opensolaris.org Estimated Hours: 0.0 # zfs create -o encryption=aes-256-ccm -o keyscope=dataset -o keysource=raw,file:///ds2.key tank/ds2 cannot open /ds2.key free(80d6c98): invalid or corrupted buffer stack trace: libumem.so.1''umem_err_recoverable+0x39 libumem.so.1''process_free+0xe1 libumem.so.1''free+0x17 libzfs.so.1''zfs_crypto_create+0x1c3 libzfs.so.1''zfs_create+0x25c zfs''zfs_do_create+0x495 zfs''main+0x265 zfs''_start+0x7a The above file didn...

...on/pos4obj.c update: usr/src/lib/librt/common/sched.c update: usr/src/lib/librt/common/sem.c update: usr/src/lib/librt/common/shm.c update: usr/src/lib/libscf/common/libscf_impl.h update: usr/src/lib/libsendfile/Makefile.com update: usr/src/lib/libsocket/inet/ether_addr.c update: usr/src/lib/libumem/common/linktest_stand.c update: usr/src/lib/libumem/common/misc.c update: usr/src/lib/libumem/common/stub_stand.c update: usr/src/lib/libumem/common/umem.c update: usr/src/lib/libumem/common/umem_fork.c update: usr/src/lib/libumem/common/vmem.c update: usr/src/lib/libumem/common/vmem_base.c...

...122K 1016M 0% ONLINE - -bash-3.2$ zpool key -l Key Load Error: Key already loaded. Enter in hexadecmial key for ''pool_105153_2'': ===> Enter "test" here Enter again: ===> Enter "tttt" here free(80bbd7c): invalid or corrupted buffer stack trace: libumem.so.1''umem_err_recoverable+0x39 libumem.so.1''process_free+0xe1 libumem.so.1''free+0x17 libzfs.so.1''get_passphrase+0x1bc libzfs.so.1''get_key_material+0x54 libzfs.so.1''load_key+0x59 libzfs.so.1''zpool_load_key+0x102 libzfs.so.1''zpoo...

...ow you''re looking for a bad memcpy), and it isn''t really a postmortem debugging tool - your best bet for this would be to use mdb (if the process has already crashed, and you have a core file) to get the stack and have a poke around the entrails, or to use the debugging options in libumem to narrow down any access violations if you have a reproducible test case. Adam''s blog has a good example of using libumem to track leaks; looking for bad memory access is similar. However, once you''ve narrowed down where your crash might be, DTrace and particularly speculations...

...ot;, 1023) = 12 resolvepath("/sbin/zpool", "/sbin/zpool", 1023) = 11 sysconfig(_CONFIG_PAGESIZE) = 4096 stat64("/sbin/zpool", 0x080478F8) = 0 open("/var/ld/ld.config", O_RDONLY) Err#2 ENOENT stat64("/lib/libumem.so.1", 0x080470A8) = 0 resolvepath("/lib/libumem.so.1", "/lib/libumem.so.1", 1023) = 17 open("/lib/libumem.so.1", O_RDONLY) = 3 mmapobj(3, MMOBJ_INTERPRET, 0xFEF80AE0, 0x08047114, 0x00000000) = 0 close(3)...

I am running a very simple multithreaded program (TestThread.C) which calls gethostbyname_r in several threads. My analysis of this program with both truss and DTrace suggest that is has a small leak. However, if I alter the program to have many more threads and run for a lot longer it never runs out of memory and does not carry on growing. Can anybody explain what I am missing in my analysis or

...sys/CORE amd64 # svnversion 238067M # make NOCLEAN=yes NO_CLEAN=yes buildworld [...] ===> cddl/lib (obj,depend,all,install) ===> cddl/lib/drti (obj) ===> cddl/lib/libavl (obj) ===> cddl/lib/libctf (obj) ===> cddl/lib/libdtrace (obj) ===> cddl/lib/libnvpair (obj) ===> cddl/lib/libumem (obj) ===> cddl/lib/libuutil (obj) ===> cddl/lib/libzfs (obj) ===> cddl/lib/libzpool (obj) ===> cddl/lib/drti (depend) ===> cddl/lib/libavl (depend) ===> cddl/lib/libctf (depend) ===> cddl/lib/libdtrace (depend) ===> cddl/lib/libnvpair (depend) ===> cddl/lib/libumem (depe...

...For internal to Sun people this is ardbeg.sfbay ardbeg# zpool list internal error: Bad file number Jun 19 11:10:57 ardbeg genunix: NOTICE: core_log: zpool[4895] core dumped: /var/core/zpool.4895.core zsh: IOT instruction (core dumped) zpool list ardbeg# mdb zpool.4895.core Loading modules: [ libumem.so.1 libnvpair.so.1 libuutil.so.1 libc.so.1 libsysevent.so.1 libavl.so.1 ld.so.1 ] > $c libc.so.1`_lwp_kill+7(1, 6) libc.so.1`raise+0x22(6) libc.so.1`abort+0xcd(9, 80db548, fefba000, 8042e34, fef79953, 80db96c) libzfs.so.1`zfs_verror+0xce(80db548, 7f7, fefa8b14, 8042e74) libzfs.so.1`zfs_standa...

...ated Hours: 0.0 da64-x4500b-gmp03# zpool get usage: get <"all" | property[,...]> <pool> ... the following properties are supported: PROPERTY EDIT VALUES zsh: segmentation fault (core dumped) zpool get da64-x4500b-gmp03# mdb core Loading modules: [ libumem.so.1 libc.so.1 ld.so.1 ] > $c libc.so.1`strcmp+0xde(0, fedf4860) libzfs.so.1`zprop_compare+0x4e(80e8fb0, 80e8f94) libc.so.1`qsort+0x3ec(80e8f70, 12, 4, feda9110) libzfs.so.1`zprop_iter_common+0x7a(8054670, 8074250, 0, 1, 8) libzfs.so.1`zprop_iter+0x27(8054670, 8074250, 0, 1, 8) usage+0x15f(0) zp...

Hi , I have c++ server application in solaries 10 . Day by day memory usage is growing i try to find memory leaks with MDB and DTRACE and no leaks found. how can we find reason for growing memory , can we know which memory sigment is cause for growing memory usage Thanks in Advance. Rao -- This message posted from opensolaris.org

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"> <title></title> </head> <body text="#330000" bgcolor="#ffffff"> <tt><font size="+1">I am attempting to run the sun webserver 7

I would like to profile heap usage on a per thread basis in a large application process. To do this I am tracking calls to malloc and free with the attached script. Everything seems to look OK with some simple test programmes, however, when I track the live system, the results suggest that one thread has grown by approximately 1Gb and I would be surprised if this was true because I ran pmap -x on

It seems we are hitting a boundary with zfs send/receive over a network link (10Gb/s). We can see peak values of up to 150MB/s, but on average about 40-50MB/s are replicated. This is far away from the bandwidth that a 10Gb link can offer. Is it possible, that ZFS is giving replication a too low priority/throttling it too much?

Banging my head against a Seagate 3TB USB3 drive. Its marketing name is: Seagate Expansion 3 TB USB 3.0 Desktop External Hard Drive STAY3000102 format(1M) shows it identify itself as: Seagate-External-SG11-2.73TB Under both Solaris 10 and Solaris 11x, I receive the evil message: | I/O request is not aligned with 4096 disk sector size. | It is handled through Read Modify Write but the performance

...nstall root krb-v210-4 [20:27:32 0]# mdb -p `pgrep zoneadm` Loading modules: [ ld.so.1 libc.so.1 ] > create_zfs_zonepath::bp > :c mdb: stop at create_zfs_zonepath mdb: target stopped at: create_zfs_zonepath: save %sp, -0x468, %sp mdb: You''ve got symbols! Loading modules: [ libumem.so.1 libtopo.so.1 libavl.so.1 ] > create_zfs_zonepath+0xd8::dis -n 3 create_zfs_zonepath+0xcc: ld [%fp - 0x4], %o3 create_zfs_zonepath+0xd0: mov %i5, %o1 create_zfs_zonepath+0xd4: ld [%l2 + 0xb8], %o0 create_zfs_zonepath+0xd8: call +0x165d8...