Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | crash on report generation | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Base | Reporter: | dridgway <dridgway> | ||||||||
Component: | code | Assignee: | michael.ruess | ||||||||
Status: | CLOSED DUPLICATE | QA Contact: | issues@dba <issues> | ||||||||
Severity: | Trivial | ||||||||||
Priority: | P3 | CC: | alex.thurgood, issues | ||||||||
Version: | OOo 2.0.1 | Keywords: | crash, oooqa | ||||||||
Target Milestone: | --- | ||||||||||
Hardware: | All | ||||||||||
OS: | Windows XP | ||||||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||||||
Developer Difficulty: | --- | ||||||||||
Attachments: |
|
Description
dridgway
2005-12-15 14:49:37 UTC
Created attachment 32458 [details]
buggy db
Created attachment 32460 [details]
crash dump
Created attachment 32466 [details]
Linux crash dump and Java HotSpot error log
Also reproduced on Linux (2.0.1RC4, dump attached) and Windows 2000 (2.0.0), so I don't think it's a regression. On 2.0.0 getting the crash required generating about 20 reports total, switching between the two kinds and paging through the generated report before closing. Confirming problem. Switching between the two reports caused OOo RC5 to crash after only 4 switches. Here is the output from the bash shell : # # An unexpected error has been detected by HotSpot Virtual Machine: # # SIGSEGV (0xb) at pc=0xaac56cc6, pid=17408, tid=2587417520 # # Java VM: Java HotSpot(TM) Client VM (1.4.2_09-b05 mixed mode) # Problematic frame: # C [libgcc3_uno.so+0x6cc6] # # An error report file with more information is saved as hs_err_pid17408.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Xlib: unexpected async reply (sequence 0x3d633)! /opt/openoffice.org2.0/program/soffice: line 233: 17408 Erreur de segmentation "$sd_prog/$sd_binary" "$@" So the Java fault error OOo to segfault. Setting oooqa and crash keywords and reassigning. alex Seems to be a problem in the configuration. See stack-trace 1030113 Reproducing the crash on Linux gives the stack ---8<--- #0 0x45bb4cc6 in bridges::cpp_uno::shared::UnoInterfaceProxy::free (pEnv=0x48bd7fb0, pProxy=0x4ff486f0) at /net/jumbo.germany/sol1/SRC680/src/bridges/source/cpp_uno/shared/unointerfaceproxy.cxx:67 #1 0x40a15734 in uno_revokeMappingCallback () from /export/home/sb93797/source/src680m148/so/program/libuno_cppu.so.3 #2 0x45bb4f3e in bridges::cpp_uno::shared::UnoInterfaceProxy::releaseProxy (pUnoI=0x4ff57a38) at bridge.hxx:68 #3 0x4fdb52f3 in Java_com_sun_star_bridges_jni_1uno_JNI_1proxy_finalize () from /export/home/sb93797/source/src680m148/so/program/libjava_uno.so ---8<--- which suggests that it is duplicate to #i57684#. @mru: Please check that it is indeed duplicate once a build for CWS os73 (where #i57684# is fixed) is available. . *** This issue has been marked as a duplicate of 57684 *** Closing dup. |