Issue 112523 - [w_updt.bas][tToolsHangulHanjaConversion] Dialog crashes and renders office unusable
Summary: [w_updt.bas][tToolsHangulHanjaConversion] Dialog crashes and renders office u...
Status: CLOSED DUPLICATE of issue 111065
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: DEV300m80
Hardware: All Windows XP
: P2 Trivial (vote)
Target Milestone: ---
Assignee: helge.delfs
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-18 19:41 UTC by joerg.skottke
Modified: 2013-08-07 14:44 UTC (History)
3 users (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 joerg.skottke 2010-06-18 19:41:19 UTC 
For some yet unknown and hard to reproduce reason the dialog causes the test to
interrupt, leaving the office in an unusable state causing a grand total of 67
Errors to the w_updt.bas test.

This has been observed quite a number of times but never very realiably. 
The problem strikes frequently on DEV300m77-m80 based CWS such as fwk143 and jl152.
The test case tToolsHangulHanjaConversion (w_007_.inc) has been disabled.
Comment 1 joerg.skottke 2010-06-18 19:44:04 UTC 
Setting WindowsXP, setting priority. The issue is an annoyance when trying to
test CWSes as the MWS test usually ends up in a greenstate while the CWS fails
and - as it has been seen on many CWS - is not related to the CWS at all.
Comment 2 carsten.driesner 2010-06-21 14:50:34 UTC 
cd: Stefan was able to provide more info about this severe and annoying issue.
If the test documents (hangul.html/hangul.svw) are writable the test
(w_updt.bas) will fail and the Office freezes. There are CWS which have changes
in the test code so tester would use a writable path to the testautomation
folder. Without this knowledge nobody will be able to solve this issue which is
not related to the CWS.
Comment 3 helge.delfs 2010-07-08 10:19:53 UTC 
this is all nonsense: reason for this is 111065...fixed in m84

*** This issue has been marked as a duplicate of 111065 ***
Comment 4 helge.delfs 2010-07-08 10:20:30 UTC 
close