Issue 16006 - Crash when spawn with wrong filename
Summary: Crash when spawn with wrong filename
Status: CLOSED DUPLICATE of issue 16270
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: 644m11
Hardware: PC Linux, all
: P1 (highest) Trivial (vote)
Target Milestone: ---
Assignee: thorsten.martens
QA Contact: issues@framework
URL:
Keywords: oooqa
: 16074 (view as issue list)
Depends on:
Blocks:
 
Reported: 2003-06-24 13:21 UTC by pichi
Modified: 2003-07-30 13:23 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
typescript (817 bytes, application/zip)
2003-06-25 13:46 UTC, pichi
no flags Details
typescript (no clicking before second process) (1.93 KB, application/x-gzip)
2003-06-27 13:13 UTC, pichi
no flags Details
typescript (crash during close, clicked before second process) (1.47 KB, application/x-gzip)
2003-06-27 13:18 UTC, pichi
no flags Details
typescript (crash after some PageUp) (1.95 KB, application/x-gzip)
2003-06-27 13:23 UTC, pichi
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description pichi 2003-06-24 13:21:08 UTC
Soffice crashes when is launched with bad parameters on command line and is
still runing in other instance. It's may be tryed:

soffice exist_file &
soffice nonexist_file &

It causes crash second soffice.bin with uncoverable error and froze first one.
Both soffice.bin was remain in memmory. Second can be killed by SIGTERM but fist
one must be killed by SIGKILL. When second have more paremeters (soffice
nonexist_file1 nonexist_file2 ... &) it's happend after error message with last
parameter.

It causes lost unsaved data of all previously opened files.
Comment 1 pichi 2003-06-24 13:27:25 UTC
It's detected on two diferent PC with RH9 under GNOME and IceWM. One
of these processes reports: 
sh: line 1: crash_report: command not found
Comment 2 dankegel 2003-06-25 04:21:22 UTC
Sorry, I can't reproduce this here.
Can you submit a symbolic stack traceback, please?
Instructions are at http://kegel.com/openoffice
Thanks!
- Dan
Comment 3 pichi 2003-06-25 13:42:53 UTC
I try It, but I cant get any useful information.
I was modify go script to I can pass parameters to soffice.bin

kangaroo:~ > cat gooffice 
#! /bin/bash
bin=/usr/local/OpenOffice.org1.1Beta2/program/
LD_LIBRARY_PATH=$bin gdb --args $bin/soffice.bin "$@"

and try gooffice noname but as You can see.
Comment 4 pichi 2003-06-25 13:46:55 UTC
Created attachment 7124 [details]
typescript
Comment 5 pavel 2003-06-26 21:04:18 UTC
*** Issue 16074 has been marked as a duplicate of this issue. ***
Comment 6 pichi 2003-06-27 12:56:15 UTC
I tryed download 644m11 and test it in this version.
I think it's depend of way how get focus window with previously
started office.bin. 

When I Raised this window by Alt+Tab it's frozen and Xlib: sequence
lost (0x10000 > 0x48d1) in reply type 0x0! Both processes stay in
memory and must be killed by way describet at my first description.

When I Raised this window by mouse click and I newer click in this
window before it not frozen. But if I open some file and click in the
window without any modification and after it I run second soffice with
bat args it crashes as with Alt+Tab.

When I Exit this window by clicking to frame it crash depend previous
cliking as above.
Comment 7 pichi 2003-06-27 13:03:03 UTC
Every time I was modify opened file, It was frozen not depend of
geting focus on window. I tryed start trought gdb this first proces
and I get some backtrace (after start and full load file I write word
test in this file and after this I started
/usr/local/OpenOffice.org644/program/soffice noname &)
Comment 8 pichi 2003-06-27 13:13:00 UTC
Created attachment 7180 [details]
typescript (no clicking before second process)
Comment 9 pichi 2003-06-27 13:18:24 UTC
Created attachment 7181 [details]
typescript (crash during close, clicked before second process)
Comment 10 pichi 2003-06-27 13:23:46 UTC
Created attachment 7182 [details]
typescript (crash after some PageUp)
Comment 11 dankegel 2003-06-29 20:18:01 UTC
These may be Red Hat 9-specific problems.  I'll have to update
my copy of Linux to test that idea.

Thanks for the crash logs on 644.  It'd be nice to have 'em for 1.1b2,
though.
I have no idea why gdb failed for you with the newer OpenOffice;
perhaps Valgrind would be able to generate a good stack traceback
for OpenOffice1.1beta2 even if gdb can't.  You might try that
if you don't want to wait for me to update my system :-)
Instructions at http://www.kegel.com/openoffice/#valgrind
but they're not as easy to follow as the gdb instructions... sorry...
Comment 12 dankegel 2003-07-05 18:26:52 UTC
Believe it or not, I ran into this by accident
while valgrinding for some other reason.
Try again once OOo1.1rc1 is released (next week?).
If that doesn't fix it, ask the guy who fixed issue 16270 to have a
look...

*** This issue has been marked as a duplicate of 16270 ***
Comment 13 pichi 2003-07-29 13:19:53 UTC
In 1.1rc2 solved.
Comment 14 pavel 2003-07-30 13:23:42 UTC
Closing.