Application Name: soffice.bin
Application Version: 18.104.22.1680
Application Timestamp: 4da4974b
Fault Module Name: configmgr.uno.dll
Fault Module Version: 22.214.171.1240
Fault Module Timestamp: 4da996c1
Exception Code: c0000005
Exception Offset: 00006546
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Can not optionally save any file and mandatory save does not work.
On exit, always crashes with referenced error
Q1. What were you doing when the application crashed?
Q2. Can you give us step-by-step instructions on how to reproduce the crash?
Q3. What produced this crash output? I'm not familiar with this format.
I see the problem too in a fresh build of the 3.4 branch. Carl F: no need to give any more information. For the future, not that the "APPCRASH" information you included is fairly useless for debugging, at least at this stage of our build and debugging process.
The problem in saving ODF formats (and possibly others) is a different one, and that has been fixed already (bug #36263).
Re-titling as there really aren't any different LibreOffice "apps". It's all one same soffice.bin process regardless of what Writer, Calc, Impress etc windows one happens to have open.
I don't see why BASIC would be related, setting component to just "Libreoffice".
The listed information is the auto windows dump that occurs when the crash occurs.
The crash occurs every time I save a file or exit the program.
The sequence after installation is:
1) open the program e.g. writer
2) close the program
3) The crash occurs
the second sequence is:
1) open the program e.g. writer
2) save the file
3) the crash occurs
(In reply to comment #1)
> Can not optionally save any file and mandatory save does not work.
> On exit, always crashes with referenced error
An error window appears with the following information:
Error saving the document Untitled1:
General input/output error
Then get the windows error "LibreOffice 3.4 has stopped working"
Using Windows 7 SP1 64bit
Please, no need to add any more information now that is just potentially confusing and related to other problems; I am on to the crash and debugging it and contemplating how to fix it. Anything that gives an error dialog with "General Error" etc is somn different thing, most likely caused by the already fixed Zip archive handling bug.
I was experiencing this problem when using the workaround to get swriter.exe to run, but I'm not experiencing any problems with crashing on exit with the Beta 2.
*** Bug 36454 has been marked as a duplicate of this bug. ***
Zack, it does happen in beta2 too, trust me.
*** Bug 36487 has been marked as a duplicate of this bug. ***
(In reply to comment #9)
> Zack, it does happen in beta2 too, trust me.
Yep, you're right. I'm experiencing it on my laptop now.
Windows Vista SP2 32 bit.
*** Bug 36500 has been marked as a duplicate of this bug. ***
*** Bug 36509 has been marked as a duplicate of this bug. ***
*** Bug 36532 has been marked as a duplicate of this bug. ***
*** Bug 36585 has been marked as a duplicate of this bug. ***
Fixed in what I would say is an extremely unclean manner in the 3.4 branch now. I hate to call it a "fix", but it makes the problem go away, so whatever...
(In reply to comment #16)
> Fixed in what I would say is an extremely unclean manner in the 3.4 branch now.
> I hate to call it a "fix", but it makes the problem go away, so whatever...
Hi Tor, is this fix going to make it into v3.4 Beta 3?
*** Bug 36645 has been marked as a duplicate of this bug. ***
(Originally #36532 which was marked as duplicate of 36301) The bug was fixed. Nevertheless there is still some unusual behavior, which made till 3.4.0
When the option "Load Libre Office during system startup" is checked, at startup quickstarter loads, opens its screen and stays displayed on screen. It does not disappear, although it installs itself in the tray bar. You have to turn it off manually, to remove it from the desktop. Not big deal, but that didn´t happen before this bug came up.
The same happens with XPSP3 and Vista Home Premium.
See Bug 37110. I think not related to this bug.