Bug 101142 - LibreOffice crashed with "intel_do_flush_locked failed: Bad address" when "Use OpenGL for all rendering" option enabled on Haswell Graphics
Summary: LibreOffice crashed with "intel_do_flush_locked failed: Bad address" when "Us...
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: 12.0
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-22 04:23 UTC by V字龍(Vdragon)
Modified: 2019-09-25 19:02 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Visual defect in LibreOffice when running 4.12.0-rc1-drm-tip (33.59 KB, image/png)
2017-05-22 08:37 UTC, V字龍(Vdragon)
Details
Visual defect in LibreOffice when running 4.12.0-rc1-drm-tip 2 (5.36 KB, image/png)
2017-05-22 08:38 UTC, V字龍(Vdragon)
Details
Visual defect in LibreOffice when running 4.12.0-rc1-drm-tip 3 (29.94 KB, image/png)
2017-05-22 08:38 UTC, V字龍(Vdragon)
Details

Description V字龍(Vdragon) 2017-05-22 04:23:31 UTC
## Bug Reproduce Instructions
1. Enable "Use OpenGL for all rendering" option in Tools/Options/LibreOffice/Views
1. Restart LibreOffice
1. Open a relatively complicate document and do some clicking and browsing

## Expected result
nothing happened

## Current result
LibreOffice crashed after several(<10) changing page etc. operations 

## Environment
* This is a KDE Neon based on Ubuntu 16.04, pretty much everything from stock
* LibreOffice 5.1.6.2
* Mesa: seems to be 12.0.6
Comment 1 V字龍(Vdragon) 2017-05-22 04:24:57 UTC
Output from LibreOffice:

```
W: Unknown node under /registry/extlang: deprecated
W: Unknown node under /registry/grandfathered: comments
W: Unknown node under /registry/grandfathered: comments

(soffice:16585): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",

(soffice:16585): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",

(soffice:16585): Gdk-WARNING **: gdk_window_set_icon_list: icons too large

(soffice:16585): Gdk-WARNING **: gdk_window_set_icon_list: icons too large

(soffice:16585): Gdk-WARNING **: gdk_window_set_icon_list: icons too large

** (soffice:16585): WARNING **: Invalid borders specified for theme pixmap:
        /usr/share/themes/Breeze/gtk-2.0/../assets/line-h.png,
borders don't fit within the image

** (soffice:16585): WARNING **: invalid source position for vertical gradient

** (soffice:16585): WARNING **: invalid source position for vertical gradient

(soffice:16585): Gdk-WARNING **: gdk_window_set_icon_list: icons too large

** (soffice:16585): WARNING **: invalid source position for vertical gradient

** (soffice:16585): WARNING **: invalid source position for vertical gradient

(soffice:16585): Gdk-WARNING **: gdk_window_set_icon_list: icons too large
intel_do_flush_locked failed: Bad address
Usage information:
StartModule;.uno:About;1
StartModule;.uno:OptionsTreeDialog;2
Usage information end
```
Comment 2 V字龍(Vdragon) 2017-05-22 04:57:23 UTC
Also a self-built kernel is used when reproducing the bug, which version is 4.11.0-pf2
Comment 3 V字龍(Vdragon) 2017-05-22 08:35:28 UTC
I've built a drm-tip kernel and can no longer reproduce the bug(although various undesired side-effect can be noticed but that other issue)
Comment 4 V字龍(Vdragon) 2017-05-22 08:37:35 UTC
Created attachment 131430 [details]
Visual defect in LibreOffice when running 4.12.0-rc1-drm-tip
Comment 5 V字龍(Vdragon) 2017-05-22 08:38:01 UTC
Created attachment 131431 [details]
Visual defect in LibreOffice when running 4.12.0-rc1-drm-tip 2
Comment 6 V字龍(Vdragon) 2017-05-22 08:38:23 UTC
Created attachment 131432 [details]
Visual defect in LibreOffice when running 4.12.0-rc1-drm-tip 3
Comment 7 V字龍(Vdragon) 2017-05-24 02:34:55 UTC
Nevermind, I found LibreOffice still crashing with the same error even when I'm using drm-tip kernel
Comment 8 V字龍(Vdragon) 2017-05-24 02:36:42 UTC
I've upgraded the LibreOffice to 5.3.3.2 through LibreOffice Fresh PPA software source, still having the same issue
Comment 9 GitLab Migration User 2019-09-25 19:02:15 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1596.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.