openoffice.org-DEV300_m50 SEGFAULT issue

View: New views
1 Messages — Rating Filter:   Alert me  

openoffice.org-DEV300_m50 SEGFAULT issue

by Saifi Khan-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi:

openoffice.org-DEV300_m50 compiled from the source code seems to
SEGFAULT after usage for an hour or so.

i've configured the starting memory allocation to 512MB and 20Mb
per object.

On receiving  soffice.bin.core file, i ran gdb and the following
trace was collected.

gdb /home/saifi/soffice.bin.core /usr/local/openoffice.org-DEV300_m50/openoffice.org3/program/soffice.bin
GNU gdb 6.1.1 [FreeBSD]
...
...
#0  0x280c63d2 in rtl_cache_alloc ()
   from /usr/local/openoffice.org-DEV300_m50/openoffice.org3/program/../basis-link/ure-link/lib/libuno_sal.so.3
#1  0x280c5b59 in rtl_allocateMemory ()
   from /usr/local/openoffice.org-DEV300_m50/openoffice.org3/program/../basis-link/ure-link/lib/libuno_sal.so.3
#2  0x08048efd in operator delete ()
#3  0x08049034 in operator new ()
#4  0x283c726f in cppu::OPropertySetHelper::OPropertySetHelper ()
   from /usr/local/openoffice.org-DEV300_m50/openoffice.org3/program/../basis-link/ure-link/lib/libuno_cppuhelpergcc3.so.3
#5  0x283db2c4 in cppu::createSingleFactory ()
   from /usr/local/openoffice.org-DEV300_m50/openoffice.org3/program/../basis-link/ure-link/lib/libuno_cppuhelpergcc3.so.3
#6  0x283d6f6d in cppu::createSingleRegistryFactory ()
   from /usr/local/openoffice.org-DEV300_m50/openoffice.org3/program/../basis-link/ure-link/lib/libuno_cppuhelpergcc3.so.3
#7  0x2ab242e6 in component_writeInfo () from /usr/local/openoffice.org-DEV300_m50/openoffice.org/ure/lib/bootstrap.uno.so
#8  0x2ab2581d in component_writeInfo () from /usr/local/openoffice.org-DEV300_m50/openoffice.org/ure/lib/bootstrap.uno.so
#9  0x2ab23fad in component_writeInfo () from /usr/local/openoffice.org-DEV300_m50/openoffice.org/ure/lib/bootstrap.uno.so
#10 0x2ab23861 in component_writeInfo () from /usr/local/openoffice.org-DEV300_m50/openoffice.org/ure/lib/bootstrap.uno.so


The complete trace may be seen here
http://twincling.pastebin.com/f51b82168

Can somebody point out a way to work around this issue or
perhaps a patch that i can apply to fix this issue ?

Thanks in advance.


thanks
Saifi.