Issue 50188 - Accessibility: Crash in table wizard in special case
Summary: Accessibility: Crash in table wizard in special case
Status: CLOSED FIXED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: 680m107
Hardware: All All
: P2 Trivial (vote)
Target Milestone: OOo 2.0.1
Assignee: christoph.lukasiak
QA Contact: issues@dba
URL:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2005-06-01 15:09 UTC by christoph.lukasiak
Modified: 2006-05-31 14:29 UTC (History)
1 user (show)

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


Attachments
Stack of a m124 installation (6.18 KB, text/plain)
2005-08-17 15:14 UTC, berend.cornelius
no flags Details
The crash in vcl window descructor. (2.17 KB, text/plain)
2005-08-19 17:21 UTC, mikhail.voytenko
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description christoph.lukasiak 2005-06-01 15:09:06 UTC
requirements: JRE 1.5.0_03 with Accessbridge 2.0beta1 and switched on
accessibility (support assistive tools)

1. create a standard (hsql) data source 
2. start the table wizard and check cathegory: personal
3. choose all fields, push: next, next, finish

-> office crashes

clu: works fine with different other java versions or access bridges (as i have
tried) - seems that only this combination crashes - this requirements are common
used in accessibility area (repro also on the pc of es and wg)
Comment 1 christoph.lukasiak 2005-06-01 15:11:18 UTC
insert keyword: accessibility
Comment 2 berend.cornelius 2005-08-17 15:14:51 UTC
Created attachment 28854 [details]
Stack of a m124 installation
Comment 3 berend.cornelius 2005-08-17 15:23:41 UTC
BC->MAV: According to MBA this is yours. Please see Stacktrace attached
Comment 4 mikhail.voytenko 2005-08-19 17:20:20 UTC
I can not reproduce the originally provided stacktrace, and the stacktrace
itself does not provide enough information even to identify the place of the
crash in sfx2.

In my case the office allways crashed with the call stack attached below. The
crash happens in vcl window destructor because the window seems to be closed
already. SSA suspected that one of parent windows could be closed without
closing the dialog control, as result the control window was closed without
notifying the control.

MAV->FS: The control and a dbaccess part of the dialog seems to be your area,
could you please take a look.
Comment 5 mikhail.voytenko 2005-08-19 17:21:47 UTC
Created attachment 28933 [details]
The crash in vcl window descructor.
Comment 6 Frank Schönheit 2005-08-22 08:51:54 UTC
fs->oj: ColumnControlWindow not properly cleaned up? Or accessing some
already-dead children in it's dtor?
Comment 7 Frank Schönheit 2005-08-22 09:07:42 UTC
now really re-assigning ....
Comment 8 ocke.janssen 2005-08-22 11:12:24 UTC
Fixed in cws dba201c
Comment 9 christoph.lukasiak 2005-10-05 10:43:30 UTC
clu->oj: like we have spoken, there is another case to check, if it is also
fixed with your fix (you can repro it on the 'gnomeland' pc or on pc of wg)

requirements: look like a problem with JDS & Gnome (repro on two jds & gnome pc
- not repro on two suse pc with 680m130 and 131)

1. create a standard (hsql) data source 
2. start the table wizard and select all proposed fields (by default)
3.push: 'next' several times, then 'finish'
=> office crashes (sometimes freezes)

like we have spoken, i will send you the error report number when it is
available (until now not appear in report tool)

Comment 10 christoph.lukasiak 2005-10-05 10:50:50 UTC
clu->oj: like we have spoken, there is another case to check, if it is also
fixed with your fix (you can repro it on the 'gnomeland' pc or on pc of wg)

requirements: look like a problem with JDS & Gnome (repro on two jds & gnome pc
- not repro on two suse pc with 680m130 and 131)

1. create a standard (hsql) data source 
2. start the table wizard and select all proposed fields (by default)
3.push: 'next' several times, then 'finish'
=> office crashes (sometimes freezes)

like we have spoken, i will send you the error report number when it is
available (report is sended, but until now not appeared in report tool)
Comment 11 ocke.janssen 2005-10-12 06:45:54 UTC
Please verify. Thanks.

re-open issue and reassign to clu@openoffice.org
Comment 12 ocke.janssen 2005-10-12 06:47:09 UTC
reassign to clu@openoffice.org
Comment 13 ocke.janssen 2005-10-12 06:47:48 UTC
reset resolution to FIXED
Comment 14 ocke.janssen 2005-10-12 06:55:27 UTC
reassign to clu@openoffice.org
Comment 15 ocke.janssen 2005-10-12 06:55:36 UTC
reset resolution to FIXED
Comment 16 christoph.lukasiak 2005-10-19 15:10:48 UTC
verified in cws

=> both cases fixed (tested on jds/gnome and winxp with proper environment)
Comment 17 christoph.lukasiak 2005-11-08 13:02:02 UTC
verified in master (src680m138)