Issue 2153 - crash after content input
Summary: crash after content input
Status: CLOSED FIXED
Alias: None
Product: Internationalization
Classification: Code
Component: code (show other issues)
Version: 641
Hardware: All All
: P1 (highest) Trivial (vote)
Target Milestone: ---
Assignee: ooo
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks: 2139 2308
  Show dependency tree
 
Reported: 2001-11-08 16:04 UTC by Unknown
Modified: 2013-08-07 15:00 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2001-11-08 16:04:13 UTC
open writer, type some input -> OOo crashes and restarts, asking for 
   retrieving previous file. Continue typing input, same thing happens 
   again, and again, and again...

spreadsheet: crashes immediately (the instruction at "...." referenced 
   memory at "....". The memory could not be read...
Comment 1 Martin Hollmichel 2001-11-08 17:31:09 UTC
This seems to be another i18n issue. Calc/Writer crash both in
CalendarImpl::loadDefaultCalendar at xSequence->getAllCalendars.

if putting are regular i18n from SO into OOo installation set, the
writer doesn't crash.
Comment 2 ooo 2001-11-09 11:19:43 UTC
This results from the changes Bustamam did: some parts (like
localedata) of the old i18n are replaced by new code and data in
i18npool and removed from i18n. But the i18npool module is not built,
and setup is not prepared to install it, hence the crash. Furthermore,
the unotools i18n wrappers are not prepared to load services from a
libi18npool instead of a libi18n (which is needed for the setup not
having a factory). Thus it's not sufficient to just build and install
lib18npool. I'll find a solution next week (starting 12Nov).
Comment 3 ooo 2001-11-13 12:18:01 UTC
Changed files and revisions:

i18npool/*  head

scp/inc/gid.inc  1.233
scp/source/player/player.scp  1.38
scp/source/global/setupzip.scp  1.54

unotools/source/i18n/localedatawrapper.cxx  1.23
unotools/source/i18n/numberformatcodewrapper.cxx  1.8
Comment 4 Unknown 2001-11-13 13:02:34 UTC
The module i18npool was completely unknown to me. It does not 
have a tag. I build it now plus the updates in scp and unotools. 
It won't crash anymore now. I'll go ahead and check in the updates 
and tag i18npool. 

HOWEVER, the font size selection box seems to be messed up. It 
contains only sizes from 1 to 9 and 105. Let me know if you want 
to have an installation set for this. 

a.
Comment 5 Martin Hollmichel 2001-11-13 19:37:38 UTC
localedata_ascii.dll and localedata_CJK.dll have to be included in the
OpenOffice.org installation set
Comment 6 ingo.schmidt-rosbiegal 2001-11-14 15:05:01 UTC
IS: Okay, I added the two localedata files to the setupzip of the
OpenOffice.org. This is fixed in rev.1.55 (toplevel) and in rev.
1.51.2.2 for the branch OO641B
Comment 7 ooo 2001-11-15 12:42:03 UTC
ER: Also the following files are needed to successfully integrate the
i18npool module in OO641:

vcl/source/app/unohelp.cxx  1.23
setup2/prj/build.lst  1.4.6.1
setup2/util/makefile.mk  1.27.4.1
sip/util/makefile.mk  1.18
Comment 8 Unknown 2001-12-06 13:11:23 UTC
Hi, 

I encounter the same problem (crash after *fast* typing some input) 
in the 641C build. I ensured that the file updates logged 
earlier in this issue are in. From all files listed here, 
we have the same version or later versions in the code. 

Comment 9 ingo.schmidt-rosbiegal 2001-12-06 16:33:18 UTC
IS -> ER: The localedata files are included in the src641C. I do not know where the problem is. And I 
also could not reproduce it with the src641c from /ship/install/OOoQA for Windows, but perhaps you can 
find something.
Comment 10 ooo 2001-12-06 20:52:46 UTC
Armin, what's the stack trace of the crash? And does it happen in
Writer and Calc or just in Writer? Anyways, I don't suspect this to be
related to the original issue (crashing because no calendar was
available because of new library structures), if my assumption could
be verified we should open a new issue instead.
Comment 11 Unknown 2001-12-13 11:53:39 UTC
To be honest, I forgot what we did about it, but this bug is 
fixed. I don't mind to have this issue closed. 

a.
Comment 12 ooo 2001-12-13 15:36:45 UTC
nor do I ...
Comment 13 Unknown 2001-12-14 08:27:36 UTC
closed