Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-9095

Jenkins crashes with error in D-Bus : arguments to dbus_message_unref() were incorrect, assertion "!message->in_cache" failed in file dbus-message.c line 1397.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Critical Critical
    • core
    • RHEL 6

      Jenkins crashed. The log shows

      process 3557: arguments to dbus_message_unref() were incorrect, assertion "!message->in_cache" failed in file dbus-message.c line 1397.
      This is normally a bug in some application using the D-Bus library.
      D-Bus not built with -rdynamic so unable to print a backtrace

      This is Jenkins 1.399

          [JENKINS-9095] Jenkins crashes with error in D-Bus : arguments to dbus_message_unref() were incorrect, assertion "!message->in_cache" failed in file dbus-message.c line 1397.

          David Biesack created issue -
          sogabe made changes -
          Link New: This issue is duplicated by JENKINS-9097 [ JENKINS-9097 ]
          sogabe made changes -
          Link New: This issue is duplicated by JENKINS-9096 [ JENKINS-9096 ]

          Oleg Nenashev added a comment -

          Assigned to the core.
          Does anybody see the bug on newer Jenkins versions?

          Oleg Nenashev added a comment - Assigned to the core. Does anybody see the bug on newer Jenkins versions?
          Oleg Nenashev made changes -
          Component/s New: core [ 15593 ]
          David Biesack made changes -
          Labels New: D-Bus crash, native,
          Jesse Glick made changes -
          Labels Original: D-Bus crash, native, New: D-Bus crash native

          Daniel Beck added a comment -

          No response to comment asking for updated information in several months, so resolving as Cannot Reproduce.

          If this occurs on a then-recent version of Jenkins (and only then) reopen or file a new bug.

          Daniel Beck added a comment - No response to comment asking for updated information in several months, so resolving as Cannot Reproduce. If this occurs on a then-recent version of Jenkins (and only then) reopen or file a new bug.
          Daniel Beck made changes -
          Resolution New: Cannot Reproduce [ 5 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 139251 ] New: JNJira + In-Review [ 188410 ]

            Unassigned Unassigned
            davidbiesack David Biesack
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: