Bug 115635 - Crash in: s_environment_invoke_v EDITING
Summary: Crash in: s_environment_invoke_v EDITING
Status: RESOLVED WONTFIX
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.1.1 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: corruptProfile
Depends on:
Blocks:
 
Reported: 2018-02-11 19:14 UTC by Woody
Modified: 2018-02-21 23:20 UTC (History)
2 users (show)

See Also:
Crash report or crash signature: ["s_environment_invoke_v"]


Attachments
Character portfolio I've created (w/o publisher's permission) for the Dungeon Fantasy Roleplaying Game ©2017 by Steve Jackson Games. (54.89 KB, application/vnd.oasis.opendocument.text)
2018-02-11 19:14 UTC, Woody
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Woody 2018-02-11 19:14:18 UTC
Created attachment 139796 [details]
Character portfolio I've created (w/o publisher's permission) for the Dungeon Fantasy Roleplaying Game ©2017 by Steve Jackson Games.

This bug was filed from the crash reporting server and is br-3bad1119-2fa6-4ad7-a09b-dcaf19503026.
=========================================

Attempts to open the Cross-reference/Variable/etc. window (default CTRL+F2) fail and Writer stops responding. Windows Task Manager must be used to end the task.
Comment 1 Woody 2018-02-16 12:05:20 UTC
The "Cross-reference/Variable/etc. window" referred to is the Fields dialog box. I apologize for using incorrect terminology.
Comment 2 Woody 2018-02-16 12:09:07 UTC
This problem does not exist in the portable LO v6 version available through portableapps.com. To be clear, when using that portable version, the Fields dialog box opens as it should, and I can create a cross-reference in the same data file attached to this report.
Comment 3 Xisco Faulí 2018-02-16 14:43:13 UTC
Hi,
Thanks for reporting the issue.
So, the crash happens when you open the document and press Ctrl+F2 ?
Comment 4 Woody 2018-02-16 19:40:53 UTC
(In reply to Xisco Faulí from comment #3)
> Hi,
> Thanks for reporting the issue.
> So, the crash happens when you open the document and press Ctrl+F2 ?

Again I apologize for not giving you information you needed.

Yes. 
1. Open the file.
2. Click somewhere in the file.
3. CTRL+F2. Program stops responding. I must use Windows Task Manager to terminate the task.

I am using Windows 7 Home Premium, Service Pack 1. 

I suspect you already have the following data:
Manufacturer: Dell
Model: INSPIRON N7110
Rating: 5.9 Windows Experience Index
Processor: Intel® Core™ i7-2670QM CPU @ 2.20GHz 2.20GHz
Installed memory (RAM): 8.00 GB (7.9 GB usable)
System type: 64-bit Operating System
Pen and Touch: No Pen or Touch Input is available for this Display.

If you need more information, I'll be happy to oblige.

--Woody
Comment 5 raal 2018-02-17 06:38:01 UTC
I can not confirm with Version: 6.0.1.1 (x64), win7

For the test, could you rename your LibreOffice directory profile (see https://wiki.documentfoundation.org/UserProfile) and give it a new try? Thank you
Comment 6 Woody 2018-02-20 18:38:00 UTC
Not really certain what I was supposed to do.

Here's what I did:
1. Went to "C:\Users\<user name>\AppData\Roaming\LibreOffice\4", and copied the "user" folder to "user - ORIGINAL".

2. Renamed "user" folder to "user - RENAMED".

3. Restarted computer, and loaded LO v 6 (6.0.1.1).

4. Loaded the file I attached to this report.

5. Could not reproduce the bug.

So what happened?

--David
Comment 7 Xisco Faulí 2018-02-21 23:20:48 UTC
(In reply to Woody from comment #6)
> Not really certain what I was supposed to do.
> 
> Here's what I did:
> 1. Went to "C:\Users\<user name>\AppData\Roaming\LibreOffice\4", and copied
> the "user" folder to "user - ORIGINAL".
> 
> 2. Renamed "user" folder to "user - RENAMED".
> 
> 3. Restarted computer, and loaded LO v 6 (6.0.1.1).
> 
> 4. Loaded the file I attached to this report.
> 
> 5. Could not reproduce the bug.
> 
> So what happened?
> 
> --David

it seem your profile got corrutped. Deleting it fixed the issue.
Sometimes, it happens for unknown reasons.
Closing as RESOLVED WONTFIX