Attachment 78111 Details for Bug 63572 – valgrind log of enlightenment

valgrind log of enlightenment

e.valgrind (text/plain), 6.17 KB, created by Bruno on 2013-04-16 20:17:00 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Bruno

Created: 2013-04-16 20:17:00 UTC

Size: 6.17 KB

patch

obsolete

>==5361== Memcheck, a memory error detector
>==5361== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
>==5361== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
>==5361== Command: /usr/bin/enlightenment -valgrind=1 -valgrind-log-file=/tmp/e.valgrind
>==5361== Parent PID: 5356
>==5361== 
>==5374== 
>==5374== HEAP SUMMARY:
>==5374==     in use at exit: 12,056,538 bytes in 19,326 blocks
>==5374==   total heap usage: 36,951 allocs, 17,625 frees, 18,083,521 bytes allocated
>==5374== 
>==5375== 
>==5375== HEAP SUMMARY:
>==5375==     in use at exit: 12,056,733 bytes in 19,329 blocks
>==5375==   total heap usage: 36,954 allocs, 17,625 frees, 18,083,720 bytes allocated
>==5375== 
>==5376== 
>==5376== HEAP SUMMARY:
>==5376==     in use at exit: 12,056,930 bytes in 19,332 blocks
>==5376==   total heap usage: 36,957 allocs, 17,625 frees, 18,083,919 bytes allocated
>==5376== 
>==5377== 
>==5377== HEAP SUMMARY:
>==5377==     in use at exit: 12,057,128 bytes in 19,335 blocks
>==5377==   total heap usage: 36,960 allocs, 17,625 frees, 18,084,121 bytes allocated
>==5377== 
>==5374== LEAK SUMMARY:
>==5374==    definitely lost: 1,006 bytes in 14 blocks
>==5374==    indirectly lost: 3,120 bytes in 124 blocks
>==5374==      possibly lost: 0 bytes in 0 blocks
>==5374==    still reachable: 12,052,412 bytes in 19,188 blocks
>==5374==         suppressed: 0 bytes in 0 blocks
>==5374== Rerun with --leak-check=full to see details of leaked memory
>==5374== 
>==5374== For counts of detected and suppressed errors, rerun with: -v
>==5374== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 3 from 1)
>==5375== LEAK SUMMARY:
>==5375==    definitely lost: 1,006 bytes in 14 blocks
>==5375==    indirectly lost: 3,120 bytes in 124 blocks
>==5375==      possibly lost: 0 bytes in 0 blocks
>==5375==    still reachable: 12,052,607 bytes in 19,191 blocks
>==5375==         suppressed: 0 bytes in 0 blocks
>==5375== Rerun with --leak-check=full to see details of leaked memory
>==5375== 
>==5375== For counts of detected and suppressed errors, rerun with: -v
>==5375== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 3 from 1)
>==5376== LEAK SUMMARY:
>==5376==    definitely lost: 1,006 bytes in 14 blocks
>==5376==    indirectly lost: 3,120 bytes in 124 blocks
>==5376==      possibly lost: 0 bytes in 0 blocks
>==5376==    still reachable: 12,052,804 bytes in 19,194 blocks
>==5376==         suppressed: 0 bytes in 0 blocks
>==5376== Rerun with --leak-check=full to see details of leaked memory
>==5376== 
>==5376== For counts of detected and suppressed errors, rerun with: -v
>==5376== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 3 from 1)
>==5377== LEAK SUMMARY:
>==5377==    definitely lost: 1,006 bytes in 14 blocks
>==5377==    indirectly lost: 3,120 bytes in 124 blocks
>==5377==      possibly lost: 0 bytes in 0 blocks
>==5377==    still reachable: 12,053,002 bytes in 19,197 blocks
>==5377==         suppressed: 0 bytes in 0 blocks
>==5377== Rerun with --leak-check=full to see details of leaked memory
>==5377== 
>==5377== For counts of detected and suppressed errors, rerun with: -v
>==5377== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 3 from 1)
>==5361== Invalid write of size 4
>==5361==    at 0x40FFE90: evas_common_scale_rgba_in_to_out_clip_smooth_mmx (evas_scale_smooth_scaler_downx_downy.c:239)
>==5361==    by 0x4102D6C: evas_common_scale_rgba_in_to_out_clip_smooth (evas_scale_smooth.c:513)
>==5361==    by 0x40F9314: evas_common_rgba_image_scalecache_do (evas_image_scalecache.c:796)
>==5361==    by 0x4110153: eng_image_draw (evas_engine.c:915)
>==5361==    by 0x4077A6B: evas_object_image_render (evas_object_image.c:3042)
>==5361==    by 0x40BF34D: evas_render_mapped (evas_render.c:1160)
>==5361==    by 0x40C1ABE: evas_render_updates_internal (evas_render.c:1575)
>==5361==    by 0x41EBC83: _ecore_evas_x_render (ecore_evas_x.c:288)
>==5361==    by 0x41E81AD: _ecore_evas_idle_enter (ecore_evas.c:59)
>==5361==    by 0x4173D11: _ecore_idle_enterer_call (ecore_private.h:281)
>==5361==    by 0x41758F4: _ecore_main_loop_iterate_internal (ecore_main.c:1833)
>==5361==    by 0x4175DAE: ecore_main_loop_begin (ecore_main.c:956)
>==5361==  Address 0x7f9c000 is not stack'd, malloc'd or (recently) free'd
>==5361== 
>==5361== 
>==5361== Process terminating with default action of signal 11 (SIGSEGV)
>==5361==  Access not within mapped region at address 0x7F9D770
>==5361==    at 0x40FFE90: evas_common_scale_rgba_in_to_out_clip_smooth_mmx (evas_scale_smooth_scaler_downx_downy.c:239)
>==5361==    by 0x4102D6C: evas_common_scale_rgba_in_to_out_clip_smooth (evas_scale_smooth.c:513)
>==5361==    by 0x40F9314: evas_common_rgba_image_scalecache_do (evas_image_scalecache.c:796)
>==5361==    by 0x4110153: eng_image_draw (evas_engine.c:915)
>==5361==    by 0x4077A6B: evas_object_image_render (evas_object_image.c:3042)
>==5361==    by 0x40BF34D: evas_render_mapped (evas_render.c:1160)
>==5361==    by 0x40C1ABE: evas_render_updates_internal (evas_render.c:1575)
>==5361==    by 0x41EBC83: _ecore_evas_x_render (ecore_evas_x.c:288)
>==5361==    by 0x41E81AD: _ecore_evas_idle_enter (ecore_evas.c:59)
>==5361==    by 0x4173D11: _ecore_idle_enterer_call (ecore_private.h:281)
>==5361==    by 0x41758F4: _ecore_main_loop_iterate_internal (ecore_main.c:1833)
>==5361==    by 0x4175DAE: ecore_main_loop_begin (ecore_main.c:956)
>==5361==  If you believe this happened as a result of a stack
>==5361==  overflow in your program's main thread (unlikely but
>==5361==  possible), you can try to increase the size of the
>==5361==  main thread stack using the --main-stacksize= flag.
>==5361==  The main thread stack size used in this run was 8388608.
>==5361== 
>==5361== HEAP SUMMARY:
>==5361==     in use at exit: 12,130,492 bytes in 19,442 blocks
>==5361==   total heap usage: 37,825 allocs, 18,383 frees, 18,347,096 bytes allocated
>==5361== 
>==5361== LEAK SUMMARY:
>==5361==    definitely lost: 1,198 bytes in 22 blocks
>==5361==    indirectly lost: 4,056 bytes in 142 blocks
>==5361==      possibly lost: 160 bytes in 1 blocks
>==5361==    still reachable: 12,125,078 bytes in 19,277 blocks
>==5361==         suppressed: 0 bytes in 0 blocks
>==5361== Rerun with --leak-check=full to see details of leaked memory
>==5361== 
>==5361== For counts of detected and suppressed errors, rerun with: -v
>==5361== ERROR SUMMARY: 2 errors from 1 contexts (suppressed: 3 from 1)

Actions: View

Attachments on bug 63572: 78026 | 78109 | 78110 | 78111

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.