This might be related to Bug 114536 (similar symptoms), but I cannot tell without a crash report.

Created attachment 138823 [details]
Document (exported by Gramps) producing crash on scrolling down.

Note 1:
The attached test document was originally created to check another bug (with multiple image references in one document). That bug seems to be fixed in 6.0.0.1 (as tested on another document with multiple image), but maybe this problem was introduced by the fix?

Note 2:
The attached document claims to have 2 pages, but acutally it should only have one. (A PDF generated earlier by LO 5.2 from it shows this.)

More info:
- The windows crash dialog show the crash is in "mergedlo.dll".
- LO 5.4.3.2 is already affected.
- With this version sending a crash report works. I get following link:
crashreport.libreoffice.org/stats/crash_details/61988ffc-17df-4290-890b-06a6d742cfa5
-> Signature in vcl/source/gdi/bmpacc2.cxx:141:
BitmapReadAccess::SetPixelForN24BitTcBgr(unsigned char *,long,BitmapColor const &,ColorMask const &)

I can't reproduce it in

Version: 6.1.0.0.alpha0+
Build ID: 864ab0502a4d3506413451e8c545144c6c15d777
CPU threads: 1; OS: Windows 6.1; UI render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2017-12-28_00:54:35
Locale: es-ES (es_ES); Calc: group threaded

nor in

Versión: 5.4.3.2
Id. de compilación: 92a7159f7e4af62137622921e809f8546db437e5
Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; 
Configuración regional: es-ES (es_ES); Calc: group

is it reproducible if OpenGL is disabled?

No crash with:
Version: 6.1.0.0.alpha0+
Build ID: a9b202a6b7000e7af34f2a639ca207122a3968bf
CPU threads: 4; OS: Windows 6.3; UI render: GL; 
TinderBox: Win-x86@42, Branch:master, Time: 2017-12-26_23:10:23
Locale: nl-NL (nl_NL); Calc: CL

E12599 - Testbild on the second page shows up black with OpenGL and transparent without OpenGL

@Xisco Faulí:
This is strange. I re-downloaded my file from here, tested again -> crash.

Same with OpenGL disabled in the options.

---
I did further tests to check for the cause of the issue.
The document in question was generated from Gramps (OS genealogy software). I removed all (but one) images from the test person, then re-added them one by one. There were no issues adding an image multiple times, nor with the initial crop, nor with the page break.

Then I remembered that the original images showed different crops of the image. I tried to re-create different image crops and finally got a version which did not crash LO the way the first report did but instead produced a "Bad allocation" error window, after which LO would quit as well, but without a crash report offer at re-start.

Even more strange, just now the very same* document causes a classical APPCRASH, this time in ucrtbase.DLL. I'll attach this version too. No crash report offered.

Long story short: I am pretty sure the cause is related to the problem mentioned by me in 114808, which is a wrong crop box for images after ODF export from Gramps, due to wrong assumptions about image DPI. Likely LO chokes on a strange image distortion.

Created attachment 138827 [details]
Re-created document, produces different crash

Created attachment 138828 [details]
Stripped-down version with just 1 image (crashes LO on loading already)

Signature of version for my last tests:
Version: 5.4.3.2 (x64)
Build-ID: 92a7159f7e4af62137622921e809f8546db437e5
CPU-Threads: 4; Betriebssystem:Windows 6.1; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE); Calc: group

No crash here with the new documents...

Version: 6.1.0.0.alpha0+
Build ID: 2bf1cc7372088ec31ac5f0fb60de57feda59d3b7
CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group threaded

To be certain the reported issue is not
related to corruption in the user profile, could you please reset your
Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and
re-test?

Created attachment 138841 [details]
Screenshot of APPCRASH

Re-tested with first document in Safe mode with User Profile reset. -> Crash when reaching the second page, as usual. Screenshot attached.
No idea what's different for me.

On pc Debian x86-64 with master sources updated some days ago, I don't reproduce the crash but:
with gtk3 rendering, it's quite slow to scroll the second doc attached.
with gen rendering, my laptop froze when just trying to open the doc.

(In reply to Matthias Basler from comment #1)
> This might be related to Bug 114536 (similar symptoms), but I cannot tell
> without a crash report.

That one is now fixed and the fix is also in 6.0.0. Would you like to re-test your own document against 6.0.0 final (announcement tomorrow, RC release available already)?

(In reply to Buovjaga from comment #14)
> (In reply to Matthias Basler from comment #1)
> > This might be related to Bug 114536 (similar symptoms), but I cannot tell
> > without a crash report.
> 
> That one is now fixed and the fix is also in 6.0.0. Would you like to
> re-test your own document against 6.0.0 final (announcement tomorrow, RC
> release available already)?

Putting to NEEDINFO for the time being...

Cannot reproduce the crashes on LO 6.0.0.3 (x64, final). However I should note I am doing this test on a different PC now.

I hope WORKSFORME is the correct status for this situation.