Issue 60515

Summary:	Crash when inserting hyperlink
Product:	General	Reporter:	ostkamp <guido.ostkamp>
Component:	ui	Assignee:	Frank Schönheit <frank.schoenheit>
Status:	CLOSED DUPLICATE	QA Contact:	issues@framework <issues>
Severity:	Trivial
Priority:	P2	CC:	ace_dent, andre.schnabel, issues, Mathias_Bauer, rb.henschel
Version:	680m150	Keywords:	oooqa, regression
Target Milestone:	OOo 2.0.2
Hardware:	PC
OS:	All
Issue Type:	DEFECT	Latest Confirmation in:	---
Developer Difficulty:	---

Description ostkamp 2006-01-14 15:47:03 UTC

This error is against OOo 680m150 Build 8995 on SuSE Linux 10.0

OOo Writer crashes when trying to insert hyperlink - this was not the case in
OOo 2.0.1.

How to reproduce:

1. Start OOo
2. File->New->Textdocument
3. Insert->Hyperlink->Internet, target e.g. http://www.google.de
4. Crash often already happens to me when typing the 'd' in google.de in the
dialog box

Following output appears in window where OOo was started:
Fatal exception: Signal 11
Stack:
/usr/local/ostkamp/OOo_latest/program/libuno_sal.so.3[0x40a265b8]
/usr/local/ostkamp/OOo_latest/program/libuno_sal.so.3[0x40a266e2]
/usr/local/ostkamp/OOo_latest/program/libuno_sal.so.3[0x40a2678f]
[0xffffe420]
/usr/local/ostkamp/OOo_latest/program/libvos3gcc3.so(_Z23_OThread_WorkerFunctionPv+0x17)[0x4096aebb]
/usr/local/ostkamp/OOo_latest/program/libuno_sal.so.3[0x40a1f2d1]
/lib/tls/libpthread.so.0[0x40f11297]
/lib/tls/libc.so.6(__clone+0x5e)[0x411ad37e]
/usr/local/ostkamp/OOo_latest/program/soffice: line 228:  9740 Aborted         
       (core dumped) "$sd_prog/$sd_binary" "$@"

I tried to analyze the core, but it failed (see below):

$ file core.9740
core.9740: ELF 32-bit LSB core file Intel 80386, version 1 (SYSV), SVR4-style,
SVR4-style, from 'soffice.bin'

$ gdb /usr/local/ostkamp/OOo_latest/program/soffice.bin core.9740
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i586-suse-linux"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".

"/home/ostkamp/core.9740" is not a core dump: File format not recognized
(gdb) 

Thus I tried to modify the soffice script to run soffice.bin inside gdb from
start. This gave the following:

/usr/local/ostkamp/OOo_latest/program/soffice.gdb.bin
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i586-suse-linux"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".

(gdb) r
Starting program: /usr/local/ostkamp/OOo_latest/program/soffice.bin 
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1100199104 (LWP 9499)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit--- 
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 1127705520 (LWP 9508)]
[New Thread 1130224560 (LWP 9509)]
[New Thread 1155894192 (LWP 9510)]
[New Thread 1161030576 (LWP 9511)]
[Thread 1161030576 (LWP 9511) exited]
[New Thread 1161030576 (LWP 9513)]
[Thread 1161030576 (LWP 9513) exited]
[New Thread 1161030576 (LWP 9515)]
[Thread 1161030576 (LWP 9515) exited]
[New Thread 1161030576 (LWP 9516)]
[Thread 1161030576 (LWP 9516) exited]
[New Thread 1161030576 (LWP 9517)]
[Thread 1161030576 (LWP 9517) exited]
[New Thread 1161030576 (LWP 9518)]
[Thread 1161030576 (LWP 9518) exited]
[New Thread 1161030576 (LWP 9519)]
[Thread 1161030576 (LWP 9519) exited]
[New Thread 1161030576 (LWP 9520)]
[Thread 1161030576 (LWP 9520) exited]
[New Thread 1161030576 (LWP 9521)]
[Thread 1161030576 (LWP 9521) exited]
[New Thread 1161030576 (LWP 9522)]
[New Thread 1209613232 (LWP 9523)]
[New Thread 1211714480 (LWP 9524)]
[New Thread 1213815728 (LWP 9525)]
[New Thread 1215916976 (LWP 9526)]
[New Thread 1218268080 (LWP 9527)]
[New Thread 1220369328 (LWP 9528)]
[New Thread 1222470576 (LWP 9529)]
[New Thread 1224571824 (LWP 9530)]
[New Thread 1226673072 (LWP 9531)]
[New Thread 1228774320 (LWP 9532)]
[New Thread 1230875568 (LWP 9533)]
[New Thread 1232976816 (LWP 9534)]
[Thread 1161030576 (LWP 9522) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1230875568 (LWP 9533)]
0x40bb77a8 in ?? () from /usr/local/ostkamp/OOo_latest/program/libuno_sal.so.3
(gdb) bt
#0  0x40bb77a8 in ?? ()
   from /usr/local/ostkamp/OOo_latest/program/libuno_sal.so.3
#1  0x4096ae9e in vos::_cpp_OThread_WorkerFunction ()
   from /usr/local/ostkamp/OOo_latest/program/libvos3gcc3.so
#2  0x4096aebb in _OThread_WorkerFunction ()
   from /usr/local/ostkamp/OOo_latest/program/libvos3gcc3.so
#3  0x40a1f2d1 in osl_yieldThread ()
   from /usr/local/ostkamp/OOo_latest/program/libuno_sal.so.3
#4  0x40f11297 in start_thread () from /lib/tls/libpthread.so.0
#5  0x411ad37e in clone () from /lib/tls/libc.so.6
#6  0x495dabb0 in ?? ()
(gdb) q
The program is running.  Exit anyway? (y or n) y

Comment 1 Regina Henschel 2006-01-14 17:23:15 UTC

I can confirm the crash for German WinXP Home.

The crash only occurs, if you start the URL with http://
If you type only www.google.de, then OOo will add http:// by itself and doesn't
crash.

Crashreport was sent (rb.henschel@t-online.de)

Comment 2 Regina Henschel 2006-01-14 20:51:54 UTC

Set to P3. It is like the example "The application crashes in very special
circumstances;" in the help for 'priority'.

Crash occurs not everytime, even if I start with http://. It happens more likely
if OOo is newly started and this is the first action.

Comment 3 ostkamp 2006-01-14 23:49:04 UTC

@regina: 

The problem is 100% reproducable on my Linux box, it doesn't matter if you have
loaded a 500+ page document or work with empty document, whether you have done
other actions before or not. If you use Insert->Hyperlink then OOo either
crashes immediately or goes into an endless loop consuming 100% CPU.

Current prio P2 is acceptable to me, however.

There must have been a new instability brought into the system between OOo 2.0.1
and 680m150.

Comment 4 andreschnabel 2006-01-15 10:07:23 UTC

I can reproduce on WinXP. -> set OS accordingly.

Comment 5 michael.ruess 2006-01-16 09:16:22 UTC

The mentioned stack points to a problem in OO Framework, the crash should occur
in all components.

MRU->TM: the stack is the same as in internal #122205. Please have a look.

Comment 6 thorsten.martens 2006-01-24 09:04:44 UTC

TM->SBA: Please have a look. This is not a framework-issue because the framework
team doesnÂ´t manage the insert-hyperlink dialog or documents where hyperlinks
can be insertet.

Comment 7 stefan.baltzer 2006-01-24 13:28:15 UTC

SBA->KSO: Please proceed.
Note: This looks very much like internal issue #122205#.
Target set to OOo 2.02.

Comment 8 kai.sommerfeld 2006-01-25 13:41:06 UTC

KSO->FS: The crash is caused by your recent changes in
svtools/source/control/inettbc.cxx (revision 1.4 => integrated m147). Under
certain circumstances SvtMatchContext_Imp instances get deleted twice which
leads to memory corruption.

Comment 9 Frank Schönheit 2006-01-25 13:53:53 UTC

known as (and fixed with) issue 60881. Fix will be part of 2.0.2.

*** This issue has been marked as a duplicate of 60881 ***

Comment 10 ace_dent 2006-02-07 17:47:26 UTC

Closing duplicate.

Regards,
Andrew