Issue 56203 - Crash after using autofilter in default bibliography database
Summary: Crash after using autofilter in default bibliography database
Status: CLOSED DUPLICATE of issue 55743
Alias: None
Product: bibliographic
Classification: Code
Component: ui (show other issues)
Version: OOo 2.0
Hardware: PC Windows XP
: P2 Trivial
Target Milestone: OOo 2.0.1
Assignee: ocke.janssen
QA Contact: issues@bibliographic
URL:
Keywords: needmoreinfo
: 55982 57262 (view as issue list)
Depends on:
Blocks:
 
Reported: 2005-10-18 13:48 UTC by yunkong
Modified: 2005-11-03 08:06 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description yunkong 2005-10-18 13:48:59 UTC 
Hello,

I opened the bibliography through OpenOfficeOrg Writer 2.0 RC through the menu 
Tools --> Bibliography database. In the default bibliography database I 
entered a random text (test) and pushed Enter (or the autofilter button).
In my case the Writer and bibliography crashed without giving an error 
message. Document Recovery is started when Writer is opened again.

PC, Windows XP Professional, 1.6 GHz, 512 MB RAM.

A.Y.K. Jong
Comment 1 eric.savary 2005-10-19 14:24:21 UTC 
Could you reproduce this?
Where did you enter the word?
Comment 2 yunkong 2005-10-20 08:25:38 UTC 
Hello es,

1. Open bibliography through Writer menu --> Tools --> bibliography database
2. In the field "search key" type "test"
3. Push the autofilter button

I expected that there wouldn't be any records to see anymore in the table 
below, since they should have been filtered out.

The actual result is that bibliography crashes and with it the writer.

Regards,

A.Y.K. Jong

P.s. I tested this on a beta version 1.9.? and there the program doesn't 
crash. I don't know the precise version of that build though.
Comment 3 eric.savary 2005-10-25 08:33:37 UTC 
Reproduced on Linux too.
This happens when the searched text does not exactly (case sensitive) in the
Identifier field.
Tests:
Search key: DAN -> finds DAN00
Search key: dan -> crash
Search key: dangel -> crash
Comment 4 Oliver Specht 2005-10-25 09:11:43 UTC 
Looks like a stack overflow. bt produces lots of lines like: 
0xaf20f2a8 in dbaccess::ORowSetBase::getValue (this=0xaf38a328,
Comment 5 ocke.janssen 2005-10-25 10:10:01 UTC 
It's already fixed in cws dba201e

*** This issue has been marked as a duplicate of 55743 ***
Comment 6 ocke.janssen 2005-10-25 10:29:16 UTC 
Closing
Comment 7 Frank Schönheit 2005-10-31 15:26:17 UTC 
*** Issue 55982 has been marked as a duplicate of this issue. ***
Comment 8 yunkong 2005-11-03 08:06:21 UTC 
*** Issue 57262 has been marked as a duplicate of this issue. ***