Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #12481 (closed)

Opened 10 years ago

Closed 9 years ago

BUG: Deadlock in AbnormalExitHandler

Reported by: dlindner Owned by: dlindner
Priority: major Milestone: 5.1.0-m3
Component: Insight Version: 5.0.2
Keywords: n.a. Cc: ux@…
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description

Some exceptions/circumstances (details not clear, yet) seem to produce a deadlock in the AbnormalExitHandler?, causing Insight to freeze; see attached jstack.

Attachments (1)

jstack of insight after ROI segmented line excel export freeze.txt (16.0 KB) - added by dlindner 10 years ago.

Download all attachments as: .zip

Change History (10)

comment:1 Changed 10 years ago by jburel

  • Cc ux@… added
  • Milestone changed from Unscheduled to 5.1.0-m1

comment:2 Changed 10 years ago by dlindner

As JM mentioned: This probably wasn't a deadlock, but a ICE operation which cannot be cancelled.

comment:3 Changed 10 years ago by jamoore

I'll take another closer look at the stacktrace, but from before and just glancing now, I don't see any ongoing Ice methods.

comment:4 Changed 10 years ago by jburel

what I was indicating was that in the shutdown hook we are trying to shut down running client, if a long method has not yet returned e.g. long image rendering or a longer search, the application will freeze until the method returns. The freeze could have been due to change group or a a switch user and the proxies being deleted.

comment:5 Changed 10 years ago by jamoore

J-m, so are you thinking that there was a blocking method, then application exit began, a hang occurred, and then that method exited?

comment:6 Changed 10 years ago by jburel

That's what I suspect.

comment:7 Changed 10 years ago by jburel

  • Milestone changed from 5.1.0-m1 to 5.1.0-m2

Let see if we can find the source of the problem

comment:8 Changed 9 years ago by dlindner

  • Milestone changed from 5.1.0-m2 to 5.1.0-m3

Moved this to m3. Maybe it could also be closed? Didn't see this error happening anymore.

comment:9 Changed 9 years ago by dlindner

  • Resolution set to invalid
  • Status changed from new to closed

Set to invalid, not reproducible.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.121210 sec.)

We're Hiring!