Issue 78961 - Having Two Data Sources Causes OOo to Stop Responding on Exit
Summary: Having Two Data Sources Causes OOo to Stop Responding on Exit
Status: CLOSED DUPLICATE of issue 78362
Alias: None
Product: porting
Classification: Code
Component: MacOSX (show other issues)
Version: 680m217
Hardware: Mac Mac OS X, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: cremlae
QA Contact: issues@porting
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-27 23:24 UTC by cremlae
Modified: 2008-11-05 21:06 UTC (History)
3 users (show)

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


Attachments
Proposed patch to fix issue (a workaround?) (1.36 KB, patch)
2007-06-28 06:00 UTC, cremlae
no flags Details | Diff
fix for issue 78362 (20.26 KB, patch)
2007-06-28 10:05 UTC, Frank Schönheit
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this issue.
Description cremlae 2007-06-27 23:24:11 UTC
Attempting to use two data sources (at least those added from the address data
wizard) causes OOo to stop responding when you hide data sources or quit. To
replicate:

1) Create two text files, each with a few fields separated by a common delimiter.
2) Add them both to OpenOffice.org using File->Wizards->Address Data Source...
(twice)
3) Click on the "Data Sources" button or go to View->Data Sources.
4) View a table in each data source (e.g., if your data source is named
"Addresses," expand it, then expand "Tables," then click on the name of a table
-- do this for both data sources).
5) Try to either quit OOo or hide data sources.
Comment 1 cremlae 2007-06-28 05:58:55 UTC
I believe I have a solution. See attached file: i78961_proposed_fix_1.patch. I
am a bit worried about it because I don't fully understand what causes the
problem, and the part of the code that I am affecting is in dbaccess, which is
not part of the aquavcl01... This means (I think) either: 1) this issue is not
unique to macport, or 2) the fix is a workaround that solves a problem that
actually originates elsewhere in aquavcl01. It's also a bit fishy because I
inserted code that, according to the comment above my code, should never be run.
At least, though, this is a start.
Comment 2 cremlae 2007-06-28 06:00:22 UTC
Created attachment 46328 [details]
Proposed patch to fix issue (a workaround?)
Comment 3 pavel 2007-06-28 06:49:43 UTC
fs: Hi! Do you have an insight into this?
Comment 4 Frank Schönheit 2007-06-28 08:16:23 UTC
Sounds like a duplicate of issue 78362, which is owned by me, and not dependent
on the platform.
The patch would in general be fine as a fallback, however, it probably does not
address the root cause (which I do not yet know).
Comment 5 pavel 2007-06-28 08:24:33 UTC
cremlae: is the stack in that isse same as yours?
Comment 6 cremlae 2007-06-28 09:02:15 UTC
pjanik: Yes, the stack in that issue is the same as mine.

fs: Sorry for the duplicate issue. I had only looked under Mac for it,
originally thinking that it was specific to the port.

Should I mark this issue as "DUPLICATE" and move the proposed patch to issue 78362?
Comment 7 Frank Schönheit 2007-06-28 09:08:04 UTC
fs->cremlae: no problem with the duplicate, I'll mark it so.

For the patch: I'm currently trying to understand what's going on there (and
what the heck caused this regression), but feel free to attach your suggested
patch to issue 78362.

*** This issue has been marked as a duplicate of 78362 ***
Comment 8 cremlae 2007-06-28 09:20:24 UTC
cremlae->fs: I suppose there's not much reason to attach it since you're looking
into the real solution. Oh well! :)
Comment 9 Frank Schönheit 2007-06-28 10:05:03 UTC
Created attachment 46332 [details]
fix for issue 78362
Comment 10 Frank Schönheit 2007-06-28 10:06:03 UTC
fs->cremlae: do you mind trying whether the attached patch (which is for issue
78362) also fixes your problem?
Comment 11 cremlae 2007-06-28 17:01:40 UTC
cremlae->fs: Yep, that fixes it for me! One aside: the patch didn't work
smoothly. It failed on source/core/dataaccess/ModelImpl.hxx (even after I made
sure I had the clean file from m217), so I applied those changes manually.
Comment 12 Frank Schönheit 2007-06-29 21:42:22 UTC
fine it fixed your problem. For applying the patch: It was relative to CWS
dba23b, which is still on m214. Means I will get conflicts on resync, thanks for
warning me :)
Comment 13 Mechtilde 2008-11-05 21:06:30 UTC
close the duplicate