View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004248 | Slicer4 | Module DICOM | public | 2016-08-25 09:55 | 2017-03-29 15:34 |
Reporter | pinter | Assigned To | pinter | ||
Priority | normal | Severity | minor | Reproducibility | sometimes |
Status | closed | Resolution | fixed | ||
Product Version | Slicer 4.5.0-1 | ||||
Target Version | Slicer 4.7.0 | Fixed in Version | Slicer 4.7.0 | ||
Summary | 0004248: Scalar volume DICOM export crashes after 10-12 exports | ||||
Description | User reported crash that happens after exporting 10-12 (varies) scalar volumes, and trying to export the next one. The main points:
| ||||
Steps To Reproduce | Have >15 images in a patient node, right click image and hit export, select folder and allow export, repeat until crash after about 10 images. | ||||
Additional Information | See details in conversation | ||||
Tags | No tags attached. | ||||
Hi Csaba - Thanks for supporting the user and for capturing this in the tracker! Did you ever get a copy of the final exporter script? It's odd to me that the script doesn't crash but the user interface does. Did you get any clues on that? -Steve |
|
I haven't received the script he wrote. I will remind him again. The fact that using the script the crash does not occur suggests that it is caused by a step done by the tag editor widget. My guess would be the same as the user's: adding the exported data back to the database immediately after exporting. |
|
Interesting - do you think the issue is in the database or the tag editing widget? I'd vote for the widget - maybe it has a dangling pointer or something. Should be detectable if we can reproduce it in a debugger. |
|
I agree. Reproducing the issue will be no doubt tedious, exporting lots of series in debug mode :) I can investigate this in a time frame depending on the priority of this issue. |
|
Export.py (2,537 bytes) |
|
Attached user script to programmatically export volumes to DICOM |
|
I did some fixes today around DICOM export, and also there was a complete overhaul of subject hierarchy since reporting this issue, so wanted to check this error "while I was there". Please test it with the latest nightly (tomorrow or later), or close this issue. Thanks! |
|
Oh I just realized that I was the reporter :) |
|
I exported 5 more (30 in total), still no crash... |
|
Agreed, since there is a new implementation and we can't replicate the issue let's close this. Thanks Csaba! |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2016-08-25 09:55 | pinter | New Issue | |
2016-08-25 09:55 | pinter | Status | new => assigned |
2016-08-25 09:55 | pinter | Assigned To | => pieper |
2016-08-25 15:14 | pieper | Note Added: 0014072 | |
2016-08-26 10:51 | pinter | Note Added: 0014073 | |
2016-08-26 11:18 | pieper | Note Added: 0014074 | |
2016-08-26 11:39 | pinter | Note Added: 0014075 | |
2016-08-26 16:03 | pinter | File Added: Export.py | |
2016-08-26 16:04 | pinter | Note Added: 0014076 | |
2016-10-12 04:29 | jcfr | Target Version | Slicer 4.6.0 => Slicer 4.7.0 |
2016-10-13 02:03 | jcfr | Product Version | Slicer 4.5.1 => Slicer 4.5.0-1 |
2017-03-29 14:52 | pinter | Note Added: 0014387 | |
2017-03-29 14:52 | pinter | Status | assigned => feedback |
2017-03-29 14:52 | pinter | Note Added: 0014388 | |
2017-03-29 14:52 | pinter | Status | feedback => assigned |
2017-03-29 15:00 | pinter | Note Added: 0014389 | |
2017-03-29 15:33 | pieper | Note Added: 0014390 | |
2017-03-29 15:34 | pinter | Status | assigned => closed |
2017-03-29 15:34 | pinter | Assigned To | pieper => pinter |
2017-03-29 15:34 | pinter | Resolution | open => fixed |
2017-03-29 15:34 | pinter | Fixed in Version | => Slicer 4.7.0 |