Page MenuHomePhabricator
Create Task
Maniphest T28258

[Segmentation] Core dumped at multiple instances while Closing Project
Closed, WontfixPublic
Actions

Assigned To
kislinsk
Authored By
a178n
Jan 31 2021, 11:01 AM
Tags
Referenced Files
F2080313: no_crash.mp4
Jan 31 2021, 11:14 PM
F2080181: crash_no_segmentation.mp4
Jan 31 2021, 7:08 PM
F2080142: crash_screen.mp4
Jan 31 2021, 5:48 PM
F2080079: crash_movies.zip
Jan 31 2021, 3:03 PM
Subscribers
a178n
floca
kalali
kislinsk
• thomass

Description

Area: Segmentation

The following routines have been observed to dump the core.

Context: Load an image

  • Test 1
  1. Make sure the image name is shown in the "Data Selection"> "Patient Image" field.
  2. Go and "Close Project" > Confirm "Yes".

Result: Core dumped. MITK workbench crashes.

Context: Load an image, start Segmentation view workflow until the tools are active (not greyed out anymore).

  • Test 2
  1. Click "Close Project" without starting any segmentation tools. Project successfully closes as expected.
  2. Now, open a new image.

Result: Even before the image is rendered into the 4 planes (coronal, sagittal etc.) MITK crashes.

  • Test 3
  1. Click on any of the tools for segmentation like "Add", "Subtract" etc. Cursor shows tool icon.
  2. Now, Click "Close Project" > Confirm "Yes".

Result: Core dumped. MITK workbench crashes.

OS: Win 10

PS: If I find more crashing click-routines in Segmentation, I will update in this phabricator issue(?)

Related Objects
Search...

Event Timeline

a178n triaged this task as Normal priority.Jan 31 2021, 11:01 AM
a178n created this task.
floca raised the priority of this task from Normal to Unbreak Now!.EditedJan 31 2021, 2:14 PM
floca added a project: Missing Info.

Thanks for reporting. Several questions:

  1. did you stumble upon it by accident/random testing or was it while you went through the check lists (so is this covered by the checklist, so that we can find such errors also in other releases?)
  2. Were all crashes with the Win installer?
  3. Which segmentation view did you use? classic or multi label?
  4. Wich views are open in the workbench when you experienced the crashes?

I was not able to reproduce the problems on my machine. 🤔 Can any one else verify that problem on their system?

kislinsk added a comment.Jan 31 2021, 2:20 PM

Also, what images did you use?

kislinsk removed kislinsk as the assignee of this task.Jan 31 2021, 2:21 PM

BTW, when using "Create subtask", please make sure to also check the other form fields during task creation, as they are by default set to the same values as the parent task. In particular, remove the assignee and probably some of the subscribers. :)

a178n added a comment.EditedJan 31 2021, 3:03 PM
In T28258#219234, @floca wrote:

Thanks for reporting. Several questions:

  1. did you stumble upon it by accident/random testing or was it while you went through the check lists (so is this covered by the checklist, so that we can find such errors also in other releases?)
  2. Were all crashes with the Win installer?
  3. Which segmentation view did you use? classic or multi label?
  4. Wich views are open in the workbench when you experienced the crashes?

I was not able to reproduce the problems on my machine. 🤔 Can any one else verify that problem on their system?

Hi Ralf,

  1. It was by accident. I wanted to reset my acts so I went for "Close Project" to restart. These are not in checklists.
  2. Yes it was Windows. I tested on my personal machine.
  3. Classic. I took up that section today morning.
  4. Even though I could reproduce the abovementioned crashes-cases many times exactly, I can't exactly reproduce them now. There is some 'mysterious' change in behaviour. However, I attach 3 screen recordings herewith.

Basically, Closing a project followed by loading/opening a new image makes the workbench crash in all 3 cases.

crash_movies.zip3 MBDownload

a178n added a comment.Jan 31 2021, 3:08 PM

FYI- Since I am in windows now, I can't really see if "Core dumped" is the real error message. I merely use it synonymously with the word "Crashed".

kislinsk added a comment.Jan 31 2021, 3:34 PM

Is there any output in the terminal window right before the crashes?

a178n added a comment.EditedJan 31 2021, 5:48 PM

Nothing special that I can see. The moment it crashes, the terminal window also closes quickly. I am attaching a screen recording with the terminal screen. From this run (as in the attached video), I feel, maybe the issue/bug has nothing to do with Segmentation. I only noticed it in the context of testing 'Segmentation'.

floca added a comment.Jan 31 2021, 5:58 PM

@a178n 2 more questions:

  1. Can you also reproduce this problem with using using the data directly from the MITK-Data folder and not out of your extracted scene file?
  2. Can you reproduce the problem with the segmentation view closed. (please close the view, close the workbench and then try it with the seg view never activated) If it is not reproducable, can you reproduce it with an other view opened that has auto selection (e.g. the measurement view)?
a178n added a comment.Jan 31 2021, 7:08 PM

Hi Ralf,
Sure. I can reproduce the crash with both conditions viz. data from MITK-Data folder and with segmentation view closed. Here is the screen recording.

Still, none of you could reproduce this issue? I am surprised. Maybe it's an isolated problem with my local machine?

kislinsk added a comment.Jan 31 2021, 8:20 PM

I even extracted the same scene to reproduce your issues as close as possible but it just works for me. Can you please close the workbench, delete the DKFZ folder in %APPDATA%/../Local, and then try again? What locale do you use on your system? Maybe that's the difference.

kislinsk added a comment.Jan 31 2021, 8:22 PM

If nothing else helps, I guess the only way we can actually get closer to what happens is that you build the WorkbenchRelease configuration of the latest snapshot to be able to start the workbench in debug mode. Do you need assistance for the build?

floca added a comment.Jan 31 2021, 8:56 PM
In T28258#219276, @a178n wrote:

Still, none of you could reproduce this issue? I am surprised. Maybe it's an isolated problem with my local machine?

No. Still cannot reprocue it. Very strange.

In T28258#219277, @kislinsk wrote:

Can you please close the workbench, delete the DKFZ folder in %APPDATA%/../Local, and then try again?

Please follow that advise and check it with old app caches removed.

What locale do you use on your system? Maybe that's the difference.

Hm, could be also a possibility...

a178n added a comment.Jan 31 2021, 11:01 PM
In T28258#219277, @kislinsk wrote:

I even extracted the same scene to reproduce your issues as close as possible but it just works for me. Can you please close the workbench, delete the DKFZ folder in %APPDATA%/../Local, and then try again? What locale do you use on your system? Maybe that's the difference.

I deleted the ../Appdata/Local DKFZ cache and tried again. Same bug. No change.
Locale is Germany.

a178n added a comment.EditedJan 31 2021, 11:14 PM

I have finally found the fix! This bug is due to my GPU driver.
My laptop has an AMD Radeon dedicated GPU and MITK uses it by default for rendering its "Standard Display".
I checked the crash log using Event Viewer and found that atio6axx.dll was the culprit here. This is an AMD driver related DLL file.
I switched the default GPU for Mitk workbench to the onboard integrated graphics and that's it!
Problem solved. I am attaching the working screen recording herewith :-)

a178n added a comment.Jan 31 2021, 11:17 PM

Hi Ralf, Stefan & others involved,
I am sorry for attracting unnecessary concerns on a bug which never really existed.

kalali added a comment.EditedFeb 1 2021, 11:24 AM
In T28258#219285, @a178n wrote:

I have finally found the fix! This bug is due to my GPU driver.
My laptop has an AMD Radeon dedicated GPU and MITK uses it by default for rendering its "Standard Display".
I checked the crash log using Event Viewer and found that atio6axx.dll was the culprit here. This is an AMD driver related DLL file.
I switched the default GPU for Mitk workbench to the onboard integrated graphics and that's it!
Problem solved. I am attaching the working screen recording herewith :-)

Could you elaborate on this? This could be something we have to investigate on anyway since we can not expect typical MITK users to workaround like you did.

kislinsk closed this task as Wontfix.Feb 1 2021, 3:58 PM
kislinsk claimed this task.
In T28258#219286, @a178n wrote:

Hi Ralf, Stefan & others involved,
I am sorry for attracting unnecessary concerns on a bug which never really existed.

No need for apologies. Actually your findings are valuable input for the future. Usually we cannot do much regarding driver bugs and we triggered quite a few of them the past years as multiple OpenGL render windows in a single application isn't something you see often I guess. Glad that you were able to solve this issue and that we now know about this possible issue with AMD drivers.

MITK · MIC · IMSY · DKFZ