Bug 103501 - Crash after drag operation on graph in xlsx file
Summary: Crash after drag operation on graph in xlsx file
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.2.1.2 release
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace
Depends on:
Blocks:
 
Reported: 2016-10-25 19:03 UTC by Stephan Mantler
Modified: 2017-10-22 09:17 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
test file (101.21 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2016-10-25 19:04 UTC, Stephan Mantler
Details
screen capture showing interaction and crash (8.68 MB, video/mp4)
2016-10-25 19:16 UTC, Stephan Mantler
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Mantler 2016-10-25 19:03:06 UTC
Description:
Calc sometimes crashes upon simple interactions with graphs (simple left clicks and dragging).

Steps to Reproduce:
1. open document containing graphs
2. perform simple interactions (selecting cells, clicking on graph, ...)
3. Calc will eventually crash. Sometimes takes a few minutes of interaction.

Actual Results:  
Calc eventually crashes and offers to recover documents. Curiously, after opening successfully recovered documents for the first time it appears to be even more prone to crashing. This suggests that there is a connection to the actual view being displayed.

Expected Results:
Stability.


Reproducible: Sometimes

User Profile Reset: Yes

Additional Info:


User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12) AppleWebKit/602.1.50 (KHTML, like Gecko) Version/10.0 Safari/602.1.50
Comment 1 Stephan Mantler 2016-10-25 19:04:32 UTC
Created attachment 128267 [details]
test file

This document (cleaned of confidential information) is known to cause the described crashes.
Comment 2 Stephan Mantler 2016-10-25 19:16:51 UTC
Created attachment 128268 [details]
screen capture showing interaction and crash

short screen capture showing clicking around and simple interactions with the test data sheet and eventual crash.
Comment 3 tommy27 2016-10-26 04:39:47 UTC
I did not reproduce the bug under Win8.1 x64 using LibO 5.1.5.2 and 5.2.1.2

please consider that LibO 5.2.1.2 is an early release which is not ready for production so I think you should consider upgrading to LibO 5.2.2.2 or wait the incoming release of 5.2.3.2 to see if bug is still reproducible.

if the problem persists downgrade to 5.1.5.2 or wait the incoming release of 5.1.6.2

exact release dates available here:
http://wiki.documentfoundation.org/ReleasePlan
Comment 4 Alex Thurgood 2016-10-26 10:17:36 UTC
No repro with test file on

Version: 5.2.1.2
Build ID: 31dd62db80d4e60af04904455ec9c9219178d620
Threads CPU : 2; Version de l'OS :Mac OS X 10.12; UI Render : par défaut; 
Locale : fr-FR (fr_FR.UTF-8); Calc: group

1) I opened the XLSX test file
2) Clicked on first tab, clicked on and off several or individual cells with left mouse button.
3) In turn, selected each tab, and clicked either cells to select them, or the graphic to select, and then drag, the graphic elsewhere in the tab.
4) Repeated the same moving backwards from rightmost tab to first tab.

No crash at any time.

There must be something else in your setup that is causing this.
Comment 5 Stephan Mantler 2016-10-26 16:35:07 UTC
Crash still exists with the latest release of LibreOffice Fresh (5.2.2.2). This is under macOS Sierra with ~/Library/Application Support/LibreOffice deleted entirely.

Backtrace running with lldb (a) makes me believe this is a macOS specific (possibly Sierra specific?) issue, and (b) confirms it is apparently related to dragging, not just clicking:

brain:~ step$ cd /Applications/LibreOffice.app/Contents/MacOS/
brain:MacOS step$ lldb soffice 
(lldb) target create "soffice"
Current executable set to 'soffice' (x86_64).
(lldb) env DEBUG=1
(lldb) r
Process 71457 launched: '/Applications/LibreOffice.app/Contents/MacOS/soffice' (x86_64)
2016-10-26 16:04:10.946039 soffice[71457:61457178] WARNING: nextEventMatchingMask should only be called from the Main Thread! This will throw an exception in the future.
2016-10-26 16:04:18.293928 soffice[71457:61456321] dynamic_cast error 2: One or more of the following type_info's  has hidden visibility.  They should all have public visibility.   7SdrView, 12SdrPaintView, 10FmFormView.
Process 71457 stopped
* thread #1: tid = 0x3a9bfc1, 0x00007fff9f917888 CoreGraphics`decode_data + 4179, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=2, address=0x130936000)
    frame #0: 0x00007fff9f917888 CoreGraphics`decode_data + 4179
CoreGraphics`decode_data:
->  0x7fff9f917888 <+4179>: movw   %si, (%rbx,%rax,2)
    0x7fff9f91788c <+4183>: sarl   $0x1f, %r8d
    0x7fff9f917890 <+4187>: andl   %r8d, %r15d
    0x7fff9f917893 <+4190>: notl   %r8d
(lldb) bt
* thread #1: tid = 0x3a9bfc1, 0x00007fff9f917888 CoreGraphics`decode_data + 4179, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=2, address=0x130936000)
  * frame #0: 0x00007fff9f917888 CoreGraphics`decode_data + 4179
    frame #1: 0x00007fff9facb22e CoreGraphics`img_decode_read + 309
    frame #2: 0x00007fff9facd80d CoreGraphics`img_imagemask_read + 551
    frame #3: 0x00007fff9fad00b6 CoreGraphics`img_colormatch_read + 362
    frame #4: 0x00007fff9fad053c CoreGraphics`img_alphamerge_read + 522
    frame #5: 0x00007fff9fad493d CoreGraphics`img_data_lock + 9373
    frame #6: 0x00007fff9fad2465 CoreGraphics`CGSImageDataLock + 161
    frame #7: 0x00007fff9f95a4ba CoreGraphics`ripc_AcquireImage + 991
    frame #8: 0x00007fff9f969382 CoreGraphics`ripc_DrawImage + 1135
    frame #9: 0x00007fff9f9e499b CoreGraphics`CGContextDelegateDrawImage + 70
    frame #10: 0x00007fff9fadadb6 CoreGraphics`CGContextDrawImageWithOptions + 629
    frame #11: 0x00007fff9fadb12a CoreGraphics`CGContextDrawImage + 73
    frame #12: 0x0000000102b16dd0 libvcllo.dylib`AquaSalGraphics::drawAlphaBitmap(SalTwoRect const&, SalBitmap const&, SalBitmap const&) + 272
    frame #13: 0x0000000102a3eff3 libvcllo.dylib`SalGraphics::DrawAlphaBitmap(SalTwoRect const&, SalBitmap const&, SalBitmap const&, OutputDevice const*) + 275
    frame #14: 0x0000000102913218 libvcllo.dylib`OutputDevice::DrawDeviceAlphaBitmap(Bitmap const&, AlphaMask const&, Point const&, Size const&, Point const&, Size const&) + 728
    frame #15: 0x0000000102912a37 libvcllo.dylib`OutputDevice::DrawDeviceBitmap(Point const&, Size const&, Point const&, Size const&, BitmapEx&) + 119
    frame #16: 0x000000010291219c libvcllo.dylib`OutputDevice::DrawBitmapEx(Point const&, Size const&, Point const&, Size const&, BitmapEx const&, MetaActionType) + 1084
    frame #17: 0x0000000102911cc4 libvcllo.dylib`OutputDevice::DrawBitmapEx(Point const&, BitmapEx const&) + 148
    frame #18: 0x0000000105acb839 libdrawinglayerlo.dylib`drawinglayer::impBufferDevice::paint(double) + 681
    frame #19: 0x0000000105ad9d8a libdrawinglayerlo.dylib`drawinglayer::processor2d::VclProcessor2D::RenderUnifiedTransparencePrimitive2D(drawinglayer::primitive2d::UnifiedTransparencePrimitive2D const&) + 266
    frame #20: 0x0000000105ad6b76 libdrawinglayerlo.dylib`drawinglayer::processor2d::VclPixelProcessor2D::processBasePrimitive2D(drawinglayer::primitive2d::BasePrimitive2D const&) + 5142
    frame #21: 0x0000000105ac5f34 libdrawinglayerlo.dylib`drawinglayer::processor2d::BaseProcessor2D::process(drawinglayer::primitive2d::Primitive2DContainer const&) + 148
    frame #22: 0x0000000105ad57ce libdrawinglayerlo.dylib`drawinglayer::processor2d::VclPixelProcessor2D::processBasePrimitive2D(drawinglayer::primitive2d::BasePrimitive2D const&) + 110
    frame #23: 0x0000000105ac5f34 libdrawinglayerlo.dylib`drawinglayer::processor2d::BaseProcessor2D::process(drawinglayer::primitive2d::Primitive2DContainer const&) + 148
    frame #24: 0x00000001012ce05b libsvxcorelo.dylib`sdr::overlay::OverlayManager::ImpDrawMembers(basegfx::B2DRange const&, OutputDevice&) const + 395
    frame #25: 0x00000001012c6af4 libsvxcorelo.dylib`sdr::overlay::OverlayManagerBuffered::ImpBufferTimerHandler(Idle*) + 740
    frame #26: 0x000000010131647b libsvxcorelo.dylib`SdrDragView::ShowDragObj() + 139
    frame #27: 0x000000010130bce3 libsvxcorelo.dylib`SdrDragMove::MoveSdrDrag(Point const&) + 2627
    frame #28: 0x000000010131459e libsvxcorelo.dylib`SdrDragView::MovAction(Point const&) + 78
    frame #29: 0x00000001013033c2 libsvxcorelo.dylib`SdrCreateView::MovAction(Point const&) + 18
    frame #30: 0x00000001251d2725 libsclo.dylib`FuSelection::MouseMove(MouseEvent const&) + 181
    frame #31: 0x000000012541b80d libsclo.dylib`ScGridWindow::DrawMouseMove(MouseEvent const&) + 125
    frame #32: 0x000000012540ae81 libsclo.dylib`ScGridWindow::MouseMove(MouseEvent const&) + 1873
    frame #33: 0x0000000102882149 libvcllo.dylib`ImplHandleMouseEvent(VclPtr<vcl::Window> const&, MouseNotifyEvent, bool, long, long, unsigned long, unsigned short, MouseEventModifiers) + 4953
    frame #34: 0x0000000102883a9f libvcllo.dylib`ImplWindowFrameProc(vcl::Window*, SalEvent, void const*) + 431
    frame #35: 0x0000000102b5e6d0 libvcllo.dylib`-[SalFrameView sendMouseEventToFrame:button:eventtype:] + 1248
    frame #36: 0x00007fff9d9da8ea AppKit`-[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 4340
    frame #37: 0x00007fff9d9d942a AppKit`-[NSWindow(NSEventRouting) sendEvent:] + 541
    frame #38: 0x00007fff9d879bf5 AppKit`-[NSApplication(NSEvent) sendEvent:] + 1145
    frame #39: 0x0000000102b54fe7 libvcllo.dylib`-[VCL_NSApplication sendEvent:] + 359
    frame #40: 0x0000000102b01ad6 libvcllo.dylib`AquaSalInstance::DoYield(bool, bool, unsigned long) + 950
    frame #41: 0x0000000102a82f6e libvcllo.dylib`Application::Yield() + 78
    frame #42: 0x0000000102a82f08 libvcllo.dylib`Application::Execute() + 296
    frame #43: 0x00000001001082a0 libsofficeapp.dylib`desktop::Desktop::Main() + 7152
    frame #44: 0x0000000102a870cf libvcllo.dylib`ImplSVMain() + 79
    frame #45: 0x0000000102b014f4 libvcllo.dylib`AquaSalInstance::handleAppDefinedEvent(NSEvent*) + 84
    frame #46: 0x0000000102b54fc4 libvcllo.dylib`-[VCL_NSApplication sendEvent:] + 324
    frame #47: 0x00007fff9d160009 AppKit`-[NSApplication run] + 1002
    frame #48: 0x00007fff9d12aa8a AppKit`NSApplicationMain + 1237
    frame #49: 0x0000000102b007cd libvcllo.dylib`ImplSVMainHook(int*) + 397
    frame #50: 0x0000000102a87d5a libvcllo.dylib`SVMain() + 26
    frame #51: 0x0000000100132e8b libsofficeapp.dylib`soffice_main + 219
    frame #52: 0x0000000100000f20 soffice`main + 16
    frame #53: 0x00007fffb45a6255 libdyld.dylib`start + 1
    frame #54: 0x00007fffb45a6255 libdyld.dylib`start + 1
Comment 6 Alex Thurgood 2016-11-03 09:22:46 UTC
@Stephan : 

Please indicate which graphic chip(s) you have on your system (if more than one), and if you do have more than one, which one is being used when LibreOffice is launched.

Also please indicate whether you are using an external monitor, or an iMac 5K.
Comment 7 Stephan Mantler 2016-11-03 10:29:28 UTC
(In reply to Alex Thurgood from comment #6)
> @Stephan : 
> 
> Please indicate which graphic chip(s) you have on your system (if more than
> one), and if you do have more than one, which one is being used when
> LibreOffice is launched.
> 
> Also please indicate whether you are using an external monitor, or an iMac
> 5K.

The system is a Mac Pro (Mid 2010), macOS Sierra 10.12.1

System Info:
============

Hardware Overview
-----------------
  Model Name:	Mac Pro
  Model Identifier:	MacPro5,1
  Processor Name:	Quad-Core Intel Xeon
  Processor Speed:	2.4 GHz
  Number of Processors:	2
  Total Number of Cores:	8
  L2 Cache (per Core):	256 KB
  L3 Cache (per Processor):	12 MB
  Memory:	24 GB
  Processor Interconnect Speed:	5.86 GT/s
  Boot ROM Version:	MP51.007F.B03
  SMC Version (system):	1.39f11
  SMC Version (processor tray):	1.39f11

Graphics/Displays
-----------------
ATI Radeon HD 5770:
  Chipset Model:	ATI Radeon HD 5770
  Type:	GPU
  Bus:	PCIe
  Slot:	Slot-1
  PCIe Lane Width:	x16
  VRAM (Total):	1024 MB
  Vendor:	ATI (0x1002)
  Device ID:	0x68b8
  Revision ID:	0x0000
  ROM Revision:	113-C0160C-155
  EFI Driver Version:	01.00.436
  Displays:
    CG275W:
      Resolution:	2560 x 1440
      Pixel Depth:	32-Bit Color (ARGB8888)
      Mirror:	Off
      Online:	Yes
      Rotation:	Supported
      Automatically Adjust Brightness:	No
      Connection Type:	DisplayPort
    Cintiq 24HDT:
      Resolution:	1920 x 1200 @ 60 Hz
      Pixel Depth:	32-Bit Color (ARGB8888)
      Main Display:	Yes
      Mirror:	Off
      Online:	Yes
      Rotation:	Supported
      Automatically Adjust Brightness:	No
Comment 8 Alex Thurgood 2016-11-03 13:25:35 UTC
@Stephan : I would hasard a guess that you have been bitten by bug 100994
Comment 9 Alex Thurgood 2016-11-03 13:35:16 UTC
Please try either or both of the workarounds mentioned in bug 100994 (screen colour profile / power saving graphics performance setting), as it seems that OSX 10.12.1 hasn't fixed the problem for you, contrary to the later reports by other users in that bug.
Comment 10 Alex Thurgood 2016-11-08 08:34:03 UTC
@Stephan : your Cintiq peripheral is, if I have understood correctly, a touchscreen interactive monitor, similar to a drawing pad. You didn't mention in your report whether the problem you are seeing only occurs when the output is to the CG275W monitor or to your Cintiq touchscreen or both.

If you unplug your Cintiq, can you still reproduce the problem ? I'm just trying to nail this down a bit more as at the moment, it is hard to figure out whether the CoreGraphics code problems you are seeing are related to one or the other or both devices.
Comment 11 Stephan Mantler 2016-11-08 18:36:30 UTC
(In reply to Alex Thurgood from comment #10)
> @Stephan : your Cintiq peripheral is, if I have understood correctly, a
> touchscreen interactive monitor, similar to a drawing pad. You didn't
> mention in your report whether the problem you are seeing only occurs when
> the output is to the CG275W monitor or to your Cintiq touchscreen or both.
> 
> If you unplug your Cintiq, can you still reproduce the problem ? I'm just
> trying to nail this down a bit more as at the moment, it is hard to figure
> out whether the CoreGraphics code problems you are seeing are related to one
> or the other or both devices.


Sorry, I haven't had time to follow up on this yet (bit stressful time of the year for us). Coincidentally I have been only using LibreOffice on the Cintiq display (the way my workplace is set up this is my primary display) or at least I can't precisely remember if I have seen it happen on the other monitor as well. 

I'll see if I can trigger the bug on either with the other one disconnected. Just to be clear the bug was triggered using a 'normal' bluetooth touchpad, not via touch interaction. I'll be working more on our spreadsheets in the next week or so (hooray for bimonthly tax reports), that should give me sufficient testing time.
Comment 12 QA Administrators 2017-05-31 10:51:30 UTC Comment hidden (obsolete)
Comment 13 QA Administrators 2017-06-28 12:34:41 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA 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

Warm Regards,
QA Team

MassPing-NeedInfo-20170628