Ticket #389 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

Gobby stirbt wenn man zu einem server mit sehr langer history verbindet

Reported by: matthias.prinz@… Owned by: armin
Priority: normal Milestone:
Component: libinfinity Version: 0.1.0
Severity: normal Keywords:
Cc: Launchpad Bug:

Description (last modified by armin) (diff)

==7457== Invalid read of size 4
==7457==    at 0x4015227: (within /lib/ld-2.7.so)
==7457==    by 0x4005C59: (within /lib/ld-2.7.so)
==7457==    by 0x4007A87: (within /lib/ld-2.7.so)
==7457==    by 0x4011533: (within /lib/ld-2.7.so)
==7457==    by 0x400D5C5: (within /lib/ld-2.7.so)
==7457==    by 0x4010F4D: (within /lib/ld-2.7.so)
==7457==    by 0x4D5EC18: (within /lib/tls/i686/cmov/libdl-2.7.so)
==7457==    by 0x400D5C5: (within /lib/ld-2.7.so)
==7457==    by 0x4D5F2BB: (within /lib/tls/i686/cmov/libdl-2.7.so)
==7457==    by 0x4D5EB50: dlopen (in /lib/tls/i686/cmov/libdl-2.7.so)
==7457==    by 0x4D5B5FB: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1600.6)
==7457==    by 0x4C8DFB0: (within /usr/lib/libpango-1.0.so.0.2002.3)
==7457==  Address 0x5e84ebc is 44 bytes inside a block of size 47 alloc'd
==7457==    at 0x4022AB8: malloc (vg_replace_malloc.c:207)
==7457==    by 0x4DA1CBC: g_malloc (in /usr/lib/libglib-2.0.so.0.1600.6)
==7457==    by 0x4DBA618: g_strdup (in /usr/lib/libglib-2.0.so.0.1600.6)
==7457==    by 0x4D5B5AF: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1600.6)
==7457==    by 0x4C8DFB0: (within /usr/lib/libpango-1.0.so.0.2002.3)
==7457==    by 0x4D49607: g_type_module_use (in /usr/lib/libgobject-2.0.so.0.1600.6)
==7457==    by 0x4C8E10A: (within /usr/lib/libpango-1.0.so.0.2002.3)
==7457==    by 0x4C8E1F6: (within /usr/lib/libpango-1.0.so.0.2002.3)
==7457==    by 0x4C8E275: pango_map_get_engines (in /usr/lib/libpango-1.0.so.0.2002.3)
==7457==    by 0x4C91C9C: (within /usr/lib/libpango-1.0.so.0.2002.3)
==7457==    by 0x4C91F00: (within /usr/lib/libpango-1.0.so.0.2002.3)
==7457==    by 0x4C925DC: pango_itemize_with_base_dir (in /usr/lib/libpango-1.0.so.0.2002.3)
==7457== 
==7457== Invalid read of size 4
==7457==    at 0x4015227: (within /lib/ld-2.7.so)
==7457==    by 0x400D8C9: (within /lib/ld-2.7.so)
==7457==    by 0x4009A56: (within /lib/ld-2.7.so)
==7457==    by 0x4F44694: (within /lib/tls/i686/cmov/libc-2.7.so)
==7457==    by 0x4F44A29: _dl_sym (in /lib/tls/i686/cmov/libc-2.7.so)
==7457==    by 0x4D5EDE7: (within /lib/tls/i686/cmov/libdl-2.7.so)
==7457==    by 0x400D5C5: (within /lib/ld-2.7.so)
==7457==    by 0x4D5F2BB: (within /lib/tls/i686/cmov/libdl-2.7.so)
==7457==    by 0x4D5ED72: dlsym (in /lib/tls/i686/cmov/libdl-2.7.so)
==7457==    by 0x4D5B203: g_module_symbol (in /usr/lib/libgmodule-2.0.so.0.1600.6)
==7457==    by 0x4D5BA76: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1600.6)
==7457==    by 0x4C8DFB0: (within /usr/lib/libpango-1.0.so.0.2002.3)
==7457==  Address 0x61022bc is 44 bytes inside a block of size 47 alloc'd
==7457==    at 0x4022AB8: malloc (vg_replace_malloc.c:207)
==7457==    by 0x4006FC4: (within /lib/ld-2.7.so)
==7457==    by 0x40079C9: (within /lib/ld-2.7.so)
==7457==    by 0x4011533: (within /lib/ld-2.7.so)
==7457==    by 0x400D5C5: (within /lib/ld-2.7.so)
==7457==    by 0x4010F4D: (within /lib/ld-2.7.so)
==7457==    by 0x4D5EC18: (within /lib/tls/i686/cmov/libdl-2.7.so)
==7457==    by 0x400D5C5: (within /lib/ld-2.7.so)
==7457==    by 0x4D5F2BB: (within /lib/tls/i686/cmov/libdl-2.7.so)
==7457==    by 0x4D5EB50: dlopen (in /lib/tls/i686/cmov/libdl-2.7.so)
==7457==    by 0x4D5B5FB: g_module_open (in /usr/lib/libgmodule-2.0.so.0.1600.6)
==7457==    by 0x4C8DFB0: (within /usr/lib/libpango-1.0.so.0.2002.3)

** (gobby-0.5:7457): CRITICAL **: inf_adopted_request_log_get_request: assertion `n >= priv->begin && n < priv->end' failed

** (gobby-0.5:7457): CRITICAL **: inf_adopted_request_get_request_type: assertion `INF_ADOPTED_IS_REQUEST(request)' failed

** (gobby-0.5:7457): CRITICAL **: inf_adopted_request_get_user_id: assertion `INF_ADOPTED_IS_REQUEST(request)' failed

** (gobby-0.5:7457): CRITICAL **: inf_adopted_request_get_vector: assertion `INF_ADOPTED_IS_REQUEST(request)' failed

** (gobby-0.5:7457): CRITICAL **: inf_adopted_state_vector_causally_before_inc: assertion `first != NULL' failed
**
** ERROR:(inf-adopted-algorithm.c:909):inf_adopted_algorithm_translate_request_nocache: assertion failed: (inf_adopted_algorithm_is_reachable(algorithm, to) == TRUE)
==7457== 
==7457== ERROR SUMMARY: 31 errors from 17 contexts (suppressed: 183 from 1)
==7457== malloc/free: in use at exit: 5,936,201 bytes in 68,905 blocks.
==7457== malloc/free: 746,008 allocs, 677,103 frees, 256,360,743 bytes allocated.
==7457== For counts of detected errors, rerun with: -v
==7457== searching for pointers to 68,905 not-freed blocks.
==7457== checked 6,533,712 bytes.
==7457== 
==7457== LEAK SUMMARY:
==7457==    definitely lost: 67,488 bytes in 2,333 blocks.
==7457==      possibly lost: 307,131 bytes in 878 blocks.
==7457==    still reachable: 5,561,582 bytes in 65,694 blocks.
==7457==         suppressed: 0 bytes in 0 blocks.
==7457== Rerun with --leak-check=full to see details of leaked memory.
Aborted

Attachments

bs_design_document_1.tex.record.xml (153.9 kB) - added by anonymous 5 years ago.
requested file. generates again same error. too big for one upload, so splitted into two parts
bs_design_document_1.tex.record__PART2.xml (160.7 kB) - added by anonymous 5 years ago.
part 2

Change History

Changed 5 years ago by armin

  • description modified (diff)

Gobby should store a file called in ~/.infinote-records/$documenttitle.record.xml. Could you attach that file here, directly after it crashed, please? That might help me to fix the problem.

Changed 5 years ago by anonymous

requested file. generates again same error. too big for one upload, so splitted into two parts

Changed 5 years ago by anonymous

part 2

Changed 5 years ago by armin

  • status changed from new to closed
  • resolution set to fixed
  • version changed from 0.4.90 to 0.1.0
  • component changed from Gobby to libinfinity

Fixed in master and libinfinity-0.1.

Only the client side is affected, so you don't need to update the server for this fix.

Note: See TracTickets for help on using tickets.