View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000163 | Slicer3 | Base Code | public | 2007-12-22 18:21 | 2008-05-30 07:08 |
| Reporter | davisb | Assigned To | pieper | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | linux 2.6.22; g++ (GCC) 4.2.3 | OS | linux 2.6.22; g++ (GCC) 4.2.3 | OS Version | |
| Summary | 0000163: Slicer3 hangs on startup when passed a mrml scene as an argument | ||||
| Description | Slicer3 hangs on startup when passed a mrml scene as an argument: Slicer3-build/Slicer myScene.mrml The scene can be any scene, even <MRML></MRML>. Slicer hangs and the splash screen stays in front. It is necessary to kill the Slicer3 process. | ||||
| Additional Information | The program hangs on this line: vtkKWSplashScreen::SetProgressMessage: this->GetApplication()->ProcessPendingEvents(); which is called here: Slicer.cxx: slicerApp->SplashMessage("Connected to scene."); | ||||
| Tags | No tags attached. | ||||
|
This may be related to bugs in the X server that are triggered by something in slicer. The reported behavior doesn't occur on all platforms (doesn't happen on mac or windows). But on fedora 7 systems at SPL starting slicer with a scene on the command line can cause the whole machine to hang. There may be renders being triggered before the render window is fully configured? |
|
|
Seems to work for me now. Probably there should be a dialog indicating that the scene is loading. |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2007-12-22 18:21 | davisb | New Issue | |
| 2008-01-05 04:58 | pieper | Note Added: 0000231 | |
| 2008-01-05 04:58 | pieper | Assigned To | => pieper |
| 2008-01-05 04:58 | pieper | Status | new => assigned |
| 2008-05-30 07:08 | pieper | Note Added: 0000342 | |
| 2008-05-30 07:08 | pieper | Status | assigned => closed |
| 2008-05-30 07:08 | pieper | Resolution | open => fixed |