Opened 5 years ago

Closed 2 years ago

#10975 closed bug (fixed)

KDL while executing /bin/top in OpenJDK

Reported by: pulkomandy Owned by: axeld
Priority: normal Milestone: R1
Component: System/Kernel Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

This happened on NetSurf's continuous integration buildbot. Attaching the KDL message.

Attachments (1)

d02rD1jc.txt (4.9 KB ) - added by pulkomandy 5 years ago.
KDL log of the crash.

Download all attachments as: .zip

Change History (5)

by pulkomandy, 5 years ago

Attachment: d02rD1jc.txt added

KDL log of the crash.

comment:1 by pulkomandy, 5 years ago

Component: - GeneralSystem/Kernel
Owner: changed from nobody to axeld

comment:2 by jua, 2 years ago

To work on this ticket, it needs more information...

Is this reproducible or a one-time occurence? (In the latter case it can be cloesd as "not reproducible")

If it is reproducible:

  • What version of OpenJDK was used?
  • What application was running in OpenJDK?
  • What was done with the application that causes this? Steps to reproduce?

comment:3 by pulkomandy, 2 years ago

You can join the #netsurf IRC channel to get more direct info from the people responsable for the bot.

This issue happens from time to time on the NetSurf build bot. They are running continuous integration using Jenkins, and Haiku for one of their slaves (they would prefer cross-compiling but we didn't manage to get that working).

Jenkins runs a lot of things to build NetSurf, of course.

The affected machine is "cislave3": http://ci.netsurf-browser.org/jenkins/computer/cislave3/

It's possible that the issue was already fixed in an OpenJDK update or Haiku update, I don't think the machine was updated recently. We should probably try that first.

comment:4 by pulkomandy, 2 years ago

Resolution: fixed
Status: newclosed

Ok, according to NetSurf people, this particular problem is gone. They run into another one where OpenJDK runs out of memory and fails to spawn a thread. Let's close this, then.

Note: See TracTickets for help on using tickets.