Version-Release number of selected component: libreoffice-core-4.2.4.2-8.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/lib64/libreoffice/program/soffice.bin --writer --splash-pipe=5 crash_function: GC_clear_stack_inner executable: /usr/lib64/libreoffice/program/soffice.bin kernel: 3.14.4-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 GC_clear_stack_inner at ../../../boehm-gc/misc.c:293 #11 GC_clear_stack at ../../../boehm-gc/misc.c:341 #12 GC_generic_malloc_many at ../../../boehm-gc/mallocx.c:520 #13 GC_local_malloc_atomic at ../../../boehm-gc/pthread_support.c:341 #14 _Jv_AllocPtrFreeObj at include/java-gc.h:58 #15 _Jv_NewPrimArray at ../../../libjava/prims.cc:725 #16 JvNewCharArray at ../../../libjava/gcj/array.h:90 #17 java::lang::String::init at ../../../libjava/java/lang/natString.cc:442 #18 java.lang.String.String(char[], int, int) at /usr/src/debug/gcc-4.8.2-20131212/libjava/java/lang/String.java:221 #19 java.lang.String.String(java.lang.StringBuilder) at /usr/src/debug/gcc-4.8.2-20131212/libjava/java/lang/String.java:416
Created attachment 898303 [details] File: backtrace
Created attachment 898304 [details] File: cgroup
Created attachment 898305 [details] File: core_backtrace
Created attachment 898306 [details] File: dso_list
Created attachment 898307 [details] File: environ
Created attachment 898308 [details] File: exploitable
Created attachment 898309 [details] File: limits
Created attachment 898310 [details] File: maps
Created attachment 898311 [details] File: open_fds
Created attachment 898312 [details] File: proc_pid_status
Created attachment 898313 [details] File: var_log_messages
I was trying to edit a DB report, named Dictionary. I think I may have solved it by first renaming it to Dict, and trying again (or if it was the third restart that solved it..?)
Improssible to tell from the attached (cut) stack overflow backtrace what triggers the infinite recursion in JarURLLoader construction here (i.e., whether it could be a bug in the LibreOffice code calling into the JVM), but tentatively passing over to gcj anwyay. Andreas, you may want to consider using OpenJDK instead of GCJ in LibreOffice ("Tools - Options... - LibreOffice - Advanced - Java options").
Stephan, thank you for the suggestion, I'll try that. Also, if there's not enough data to go on, I could make an attempt at reproducing this. It's only a few rather smallish files involved. But I'd prefer to know that there's a need/want for that before I spend time on it :)
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.