Steps to reproduce: 1/ open https://wiki.documentfoundation.org/images/c/cc/Monster_gltf_model.odp 2/ select the 3D model object 3/ click on the slide outside the object current behavior: crash Crash reproduced in Version: 4.4.0.0.alpha0+ Build ID: d79d2f0ef7a0e300a3ee4be128c625121d0c4b26 Version: 4.3.2.0.0+ Build ID: 64157c4598606b094f5783804b38cfb4c901a88a Both versions build at home under Ubuntu 14.04 x86-64 Best regards.JBF
On pc Debian x86-64 with master sources updated yesterday, I don't reproduce the crash. I noticed this: warn:legacy.tools:3000:1:vcl/source/gdi/bmpacc.cxx:57: Forbidden Access to empty bitmap! warn:legacy.tools:3000:1:vcl/source/window/window.cxx:852: Window::Window(): pParent == NULL warn:vcl.opengl:3000:1:vcl/source/opengl/OpenGLContext.cxx:337: OpenGL debug message: source: API, type: error, id: 1, severity: high with message: GL_INVALID_OPERATION in glDeleteShader Would it be possible you retrieve a backtrace? Also it could be useful you indicate your graphic card. (In my case, NVIDIA Corporation GF108M [GeForce GT 525M] (rev a1))
Created attachment 104540 [details] backtrace for the master Here is a backtrace for the master. No debug symbol, hope this helps. Version: 4.4.0.0.alpha0+ Build ID: e05da0d5d5399714f52e9f6df404870a381832c8 build at home on Ubuntu 14.04 x86-64 Best regards. JBF
It seems linked to accessibility part. I'll give a try with accessibility option enabled. If you have some time, you can give a try with accessibility disabled. Anyway, let's put this to NEW since there's a bt.
Even with accessibility enabled, I don't reproduce this :-( Perhaps someone will be luckier than me :)
(In reply to comment #3) > It seems linked to accessibility part. > I'll give a try with accessibility option enabled. > If you have some time, you can give a try with accessibility disabled. I do not know how to be sure that accessibility is disabled in Ubuntu. I unchecked all accessibility settings under "System parameters" with no change. Best regards. JBF
Hi Jean-Baptiste Faure, Can you test whether you can reproduce the same problem with a movie? Maybe it is something with the media window used by both movies and 3D models.
(In reply to comment #6) > Hi Jean-Baptiste Faure, > > Can you test whether you can reproduce the same problem with a movie? > Maybe it is something with the media window used by both movies and 3D > models. Good catch !!! I tried with the test kit in bug 45081 and got the same crash. In the terminal the error and warning messages are: Warning: option --ffmpeg-threads no longer exists. Warning: option --ffmpeg-threads no longer exists. [avi @ 0x3b5f9c0] non-interleaved AVI [avi @ 0x3bd5880] non-interleaved AVI Fontconfig warning: FcPattern object size does not accept value "0" Fontconfig warning: FcPattern object size does not accept value "0" Fontconfig warning: FcPattern object size does not accept value "0" Fontconfig warning: FcPattern object size does not accept value "0" [mjpeg @ 0x3bb8ae0] No JPEG data found in image (same message x 56 times) ** (soffice:2556): WARNING **: Unknown event notification 38 ** (soffice:2556): WARNING **: Unknown event notification 36 Best regards. JBF
I change the subject, since from the back trace it seems the problem actually related to the media toolbar (used both by movies/sounds and by 3D models). It seems the crash happens when the toolbar is destroyed (clicking outside the object trigger closing the media toolbar)
The crash is surely related to accessibility. For the purpose of bug 70465 I had to create for me a new clean Unity session on my Ubuntu. Now, as I do not reproduce bug 70465 anymore, I do not reproduce this crash too. No crash anymore with the test kit of bug 45081. Best regards. JBF
(In reply to Jean-Baptiste Faure from comment #9) > The crash is surely related to accessibility. For the purpose of bug 70465 I > had to create for me a new clean Unity session on my Ubuntu. Now, as I do > not reproduce bug 70465 anymore, I do not reproduce this crash too. No crash > anymore with the test kit of bug 45081. > > Best regards. JBF So can we close this bug?
(In reply to Zolnai Tamás from comment #10) > [...] > So can we close this bug? Ok, closing as worksForMe. Best regards. JBF