Uploaded image for project: 'Pentaho Data Integration - Kettle'
  1. Pentaho Data Integration - Kettle
  2. PDI-9658

Spoon for 5.0-GA shuts down with a Seg Fault with AgileBI plugin installed (on Ubuntu and Kubuntu)

    Details

    • Story Points:
      3
    • Notice:
      When an issue is open, the "Fix Version/s" field conveys a target, not necessarily a commitment. When an issue is closed, the "Fix Version/s" field conveys the version that the issue was fixed in.

      Description

      Errors are in a couple of places:

      org.pentaho.platform.engine.core.system.PentahoSystem: PentahoSystem.ERROR_0026 - Failed to retrieve object with name "null" from the Pentaho object factory.
      org.pentaho.platform.api.engine.ObjectFactoryException: Failed to retrieve object with key [IMetadataDomainRepository]

      No bp log location saved, using default.
      [000:000] Browser XEmbed support present: 1
      [000:000] Browser toolkit is Gtk2.
      [000:000] Using Gtk2 toolkit
      No bp log location saved, using default.
      [000:002] Warning(optionsfile.cc:47): Load: Could not open file, err=2
      [000:002] No bp log location saved, using default.
      [000:002] Browser XEmbed support present: 1
      [000:002] Browser toolkit is Gtk2.
      [000:002] Using Gtk2 toolkit
      [000:000] Warning(optionsfile.cc:47): Load: Could not open file, err=2
      [000:000] No bp log location saved, using default.

      Disk Write of Local_Themes-analyzer failed:
      java.io.NotSerializableException: org.pentaho.platform.api.ui.ModuleThemeInfo

      See attached log for all errors in context.

      1. console.log
        6 kB
        Matt Tucker
      2. spoon.log
        122 kB
        Curtis Boyden

        Issue Links

          Activity

          Hide
          cboyden Curtis Boyden added a comment -

          Deleting the instaview plugin from the agile-bi plugin seems to fix this issue. Not 100% committed to that, but so far so good.

          Show
          cboyden Curtis Boyden added a comment - Deleting the instaview plugin from the agile-bi plugin seems to fix this issue. Not 100% committed to that, but so far so good.
          Show
          lboudreau Luc Boudreau added a comment - Merged pull request: https://github.com/pentaho/pentaho-analyzer/pull/30 https://github.com/pentaho/pentaho-analyzer/commit/8e37fa7e04becdec66b4107d09c49fec6f854b82
          Hide
          kwalker Kurtis Walker added a comment -

          I've been working on this for a couple weeks now. Here is a summary of what we know.

          1. The segfault happens with webkit, not with xulrunner.
          2. Inside the Instaview main page, loading the dojox.storage module was causing the segfault. It was determined the storage module is not necessary for instaview so it was removed. Instaview no longer causes a segfault at startup.
          3. Analyzer has the same problem inside agile bi. Creating any visualizations in agile-bi causes a segfault.
          4. One piece of javascript was identified that caused the segfault 80% of the time. On temporary removal of that code, the segfault just gets thrown later in the load cycle. It is also unclear why the code snippet identified would cause a segfault.
          5. The issue with Analyzer is likely unrelated to the storage module.
          6. Analyzer works with xulrunner 1.9, but instaview loads a blank page. The javascript crashes midway because of a null pointer exception. The null reference has a correct value when run using webkit or with other browsers outside of SWT.
          7. Using the Browser from the swt library(not SwtBrowser, which is pentaho specific) and webkit in a test harness does not create a segfault when loading instaview or analyzer.
          8. Xulrunner 1.9 is not part of the ubuntu repositories, so it is not trivial to switch to xulrunner.

          Show
          kwalker Kurtis Walker added a comment - I've been working on this for a couple weeks now. Here is a summary of what we know. 1. The segfault happens with webkit, not with xulrunner. 2. Inside the Instaview main page, loading the dojox.storage module was causing the segfault. It was determined the storage module is not necessary for instaview so it was removed. Instaview no longer causes a segfault at startup. 3. Analyzer has the same problem inside agile bi. Creating any visualizations in agile-bi causes a segfault. 4. One piece of javascript was identified that caused the segfault 80% of the time. On temporary removal of that code, the segfault just gets thrown later in the load cycle. It is also unclear why the code snippet identified would cause a segfault. 5. The issue with Analyzer is likely unrelated to the storage module. 6. Analyzer works with xulrunner 1.9, but instaview loads a blank page. The javascript crashes midway because of a null pointer exception. The null reference has a correct value when run using webkit or with other browsers outside of SWT. 7. Using the Browser from the swt library(not SwtBrowser, which is pentaho specific) and webkit in a test harness does not create a segfault when loading instaview or analyzer. 8. Xulrunner 1.9 is not part of the ubuntu repositories, so it is not trivial to switch to xulrunner.
          Hide
          kwalker Kurtis Walker added a comment -

          We've determined that having the google talk plugin installed is the root cause of this issue, even though we don't use that plugin for anything. There is a simple workaround to disable the plugin by making /opt/google/talkplugin un-readable. The caveat would be any browser functionality that depends on google talk would not work. We could detect when the user has the talk plugin installed and warn them that they are likely to encounter this issue.

          Show
          kwalker Kurtis Walker added a comment - We've determined that having the google talk plugin installed is the root cause of this issue, even though we don't use that plugin for anything. There is a simple workaround to disable the plugin by making /opt/google/talkplugin un-readable. The caveat would be any browser functionality that depends on google talk would not work. We could detect when the user has the talk plugin installed and warn them that they are likely to encounter this issue.
          Hide
          jbleuel Jens Bleuel added a comment -

          Problematic frame: C [libjavascriptcoregtk-1.0.so.0+0x2fbb41] is reported over here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=409260
          --> The bug is reproducible with Eclipse 3.8.2, 4.2.2 and 4.3 RC2 when using WebKit 1.8.3. It is not observed when using WebKit 1.10.2.
          [...] it happens very often on Ubuntu and Kubuntu [...]

          Show
          jbleuel Jens Bleuel added a comment - Problematic frame: C [libjavascriptcoregtk-1.0.so.0+0x2fbb41] is reported over here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=409260 --> The bug is reproducible with Eclipse 3.8.2, 4.2.2 and 4.3 RC2 when using WebKit 1.8.3. It is not observed when using WebKit 1.10.2. [...] it happens very often on Ubuntu and Kubuntu [...]

            People

            • Assignee:
              Unassigned
              Reporter:
              cboyden Curtis Boyden
            • Votes:
              1 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Agile