for me not reproducible with LO 4.3.0.4 (Win 8.1), maybe this is a Linux only issue?

On pc Debian x86-64 with master sources updated today, I couldn't reproduce the crash.
Sophie: For the test, could you attach the file? (just to check if there could be something specific on your file)

Created attachment 103795 [details]
Document that crashes on preview

Hi Julien, any document crashes, I joined one that I just created and it crashes too. Set to unconfirmed - Sophie

Tired to reproduce, but couldnt on Linux Mint 13 and Ubuntu 14.04. :(

Version: 4.4.0.0.alpha0+
Build ID: 42cd7a8a26201fa1db98d6498198db23abef87fc
TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:master, Time: 2014-07-31_21:12:5

Sorry, I don't reproduce either the crash with the file :-(

Would you have any accessibility option enabled? If yes, could you disable it/them for the test?

Is this still happening with you sophie? Do you know how to produce a backtrace, so the devs can look into what is causing the problem?

Hi, tested right now with Debian 6 and Version: 4.4.0.0.alpha0+
Build ID: b6da6a887a0417be02e123a6d19837123e58b94f
TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:master, Time: 2014-08-09_07:47:21. And I still reproduce. 
@Julien, none of the accessibility options on my system are checked and Orca is not active, do you know of what I should check? Thanks - Sophie

About accessibility, I don't know much about it; I just know it can triggers some bugs.

Now, you may rename/remove your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#GNU.2FLinux) and retrieve a backtrace (https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace).

Hi Julien, my profile is a clean one each time I make tests. I'll try to get backtrace, unfortunately the dbg snapshots available on @45 and @46 don't launch on my Ubuntu and Debian...

Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INVALID
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
 
Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team

Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

-- The LibreOffice QA Team 

This INVALID Message was generated on: 2015-05-06

Warm Regards,
QA Team