Issue 120728

Summary: All documents crash after being open for a short time
Product: General Reporter: Shawn Moyer <shawn.moyer78>
Component: codeAssignee: AOO issues mailing list <issues>
Status: CLOSED DUPLICATE QA Contact:
Severity: Major    
Priority: P3 CC: arielch, ish_ica, issues, traes
Version: 3.4.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Issue Depends on: 121625    
Issue Blocks:    

Description Shawn Moyer 2012-08-27 18:00:28 UTC 
Anytime I open a .doc or .odt file it will only stay open for about a minute and then crash. I can close out and recover the document but this is very time consuming and slow. Once it is recovered and opened again it will crash again about a minute later. This never happened in earlier versions.
Comment 1 Jessica 2012-10-28 02:12:56 UTC 
Ever since I installed the update to 3.4.1, I haven't had a document stay open for more than 30 seconds. I can't create a document or open an existing one without it crashing. Please fix this issue ASAP.
Comment 2 Ariel Constenla-Haile 2012-10-28 02:40:04 UTC 
Please read the release notes: http://www.openoffice.org/development/releases/3.4.1.html#AOO3.4.1ReleaseNotes-KnownIssues

Apache OpenOffice 3.4.0 and 3.4.1 manage the user profile differently than previous versions. The old user profile is automatically converted so that users can keep their extensions and settings. In a minority of cases, especially with highly customized profiles (many extensions or customizations) the conversion doesn't succeed. Common symptoms are: frequent application crashes, problems with dictionaries or thesaurus, OpenOffice starting and crashing after a few seconds. To solve this, just reset/rename your user profile as explained in the official OpenOffice forum. http://user.services.openoffice.org/en/forum/viewtopic.php?t=12426
Comment 3 Rob Weir 2013-02-13 01:56:38 UTC 
No update since October.  Without further information I'm marking this as a duplicate of the 3.4 profile issue.

*** This issue has been marked as a duplicate of issue 121625 ***