Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | template crashes Windows completely | ||||||
---|---|---|---|---|---|---|---|
Product: | Writer | Reporter: | ingenstans | ||||
Component: | code | Assignee: | h.ilter | ||||
Status: | CLOSED FIXED | QA Contact: | issues@sw <issues> | ||||
Severity: | Trivial | ||||||
Priority: | P2 | CC: | issues | ||||
Version: | 680m17 | ||||||
Target Milestone: | --- | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
ingenstans
2003-12-30 13:58:06 UTC
Created attachment 12192 [details]
the killer template
I append his original report to the user list, since it is a pretty clear description. ---- Start original report ----- I've just spent 6 hours watching my ver. 1.1.0 OOo lock up my Win-XP OS, over and over. Here's how I get it to happen: I have a simple template which I've been using for some days. Earlier today, I made some minor changes to it, saved it, then tried to load it into an existing file (main menu: Format > Styles > Load). OOo grabbed most of the CPU cycles, and everything else ground virtually to a halt. There we sat for some minutes. I finally invoked Task Manager and bombed OOo off. Even that effort was breathtakingly slow. After some futzing around, I attempted to rebuild the template from scratch. What's in it is merely 10 levels of numbered headers and a few other things, with a total length of less than one page. At first this new template worked - at that point it was half build. When I got more or less back to where I was before, the lockups began all over again. I tried every trick I could think of. Six hours of trying. I've never seen anything achieve this degree of lock up on WinXP. At one point I couldn't even get to Task Manager, and had to do a hard reset - a pretty rare thing with WinXP. So...this template, which is integral to a lot of my word processing, appears to be a real OOo killer. I have not the slightest clue why OOo can't handle it. It's just not that much. Seems like someone in the know ought to look at this. changed OS to "all" until it's shown to work anywhere, since if it's bust on Windows 2000, XP, and Linux, it's probably bust everywhere. May I suggest that the version be changed to 1.1 rather than the build number. I can confirm that it definitely hangs OOo1.1.0 up under RH9 HI->FME: Please analyse whether this issue is an pp candidate. FME: Fixed in sw/source/core/text/porfld.cxx rev. 1.41.10.3 (cws swq02) FME: Could also be fixed for pp. Reassigned to QA. We have a regression to 1.0 => PP candidate Set to 1.1.2 In discuss with TZ retarget to OOo 1.1.1 FME: !!!No regression!!! FME: Fixed in sw/source/core/text/porfld.cxx rev. 1.37.200.2.16.1 (cws ooo111fix2) FME: Please verify in ooo111fix2 and swq02. Verified with cws: swq02 = ok Waiting for cws: ooo111fix2 Verified with cws ooo111fix2 = ok Waiting for integrated swq02 Target changed to OOo 2.0 Meanwhile verified with integrated srx645_m27s2-1_01.8739 = ok Retarget again to OOo 1.1.1 for the statistic. Verified with integrated 680m25 = ok |