Bug 39060 - crash with autotext holding database field
Summary: crash with autotext holding database field
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
Master old -3.6
Hardware: Other All
: high major
Assignee: Cor Nouws
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2011-07-08 01:32 UTC by Cor Nouws
Modified: 2011-10-17 03:38 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cor Nouws 2011-07-08 01:32:44 UTC
1. start new document
2. enter some paragraphs
3. enter table with e.g. 4 rows
4. open databrouser (F4) and Bibliography
5. drag some fields in the table
6. select table + some pars above/below
7. Ctrl-F3, select MyAutotext, give name tstCrash (or so ;-) )
8. Choose Autotext, New, Close
9. New document, Enter
10. Ctrl-F3, select tstCrash > insert
  > crash

well, at least the first time I did it.
(had some other crashes when working with database fields / autotext - so definitely some crashes will happen soon..)
Comment 1 Cor Nouws 2011-07-08 01:38:07 UTC
also happened: inserting of the autotext was OK, but crash was on saving.
Comment 2 Jeffrey 2011-07-10 22:11:57 UTC
Failed to reproduce on my version of the master. Followed the steps exactly. Pulling the latest one now.

Thanks for the thorough steps. From the sound of it, it looks like this problem does not occur regularly? Is there any way you can provide a sample attachment in which the crash applied for you? Also, when it crashes, can you generate a backtrace on the problem? It would be greatly helpful. Here are the steps: http://wiki.documentfoundation.org/BugReport. Read "How to Get Backtrace".

Thanks!
Comment 3 Cor Nouws 2011-08-15 08:21:27 UTC
Hi Jeffrey,

Do not se a problem on recent build from master (Build ID: 51e0d9a-4eb4f62-260b7c1).
Will try later again. And then hopefully close ;-)
Comment 4 Julien Nabet 2011-10-16 13:11:37 UTC
I tested with Master branch updated today, I didn't get a crash but there are some errors logs :

During the creation of the autotext :
Error: file:///home/maryline/compile-libreoffice/libo/solver/unxlngi6/installation/opt/program/../basis-link/program/resource/swen-US.res
Class: 273, Id: 0. Cannot load resource! 
Resource Stack
 From File /home/maryline/compile-libreoffice/libo/tools/source/rc/resmgr.cxx at Line 817
Error: <SwDoc::createListForListStyle(..)> - a list for the provided list style name already exists. Serious defect -> please inform OD. From File /home/maryline/compile-libreoffice/libo/sw/source/core/doc/docnum.cxx at Line 2526
Error: No medium is provided! From File /home/maryline/compile-libreoffice/libo/sw/source/filter/xml/wrtxml.cxx at Line 90

During the use of the autotext :
Error: <SwDoc::createListForListStyle(..)> - a list for the provided list style name already exists. Serious defect -> please inform OD. From File /home/maryline/compile-libreoffice/libo/sw/source/core/doc/docnum.cxx at Line 2526
Error: <SwXNumberingRules::getPropertyValue(..)> - no default list id found. Serious defect -> please inform OD. From File /home/maryline/compile-libreoffice/libo/sw/source/core/unocore/unosett.cxx at Line 2234
Error: no default list id found at chapter numbering rules instance. Serious defect -> please inform OD. From File /home/maryline/compile-libreoffice/libo/xmloff/source/text/txtimp.cxx at Line 966
Error: <SwXNumberingRules::getPropertyValue(..)> - no default list id found. Serious defect -> please inform OD. From File /home/maryline/compile-libreoffice/libo/sw/source/core/unocore/unosett.cxx at Line 2234
Error: no default list id found at chapter numbering rules instance. Serious defect -> please inform OD. From File /home/maryline/compile-libreoffice/libo/xmloff/source/text/txtimp.cxx at Line 966

I possibly made something wrong but anyway there's no crash and the autotext seems to work.

Cor, have you succeeded in reproducing the crash lately ?
Comment 5 Cor Nouws 2011-10-17 03:38:00 UTC
Hi Julien,

Just tested on Build ID: 4456143-f6a1fc5-e1a2fb3
And again it is OK. So fixed in the mean time

The errors you mention... maybe something for Cedric?
For now I set to fixed