Difference between revisions of "Snapshots"
From Slicer Wiki
m (→Known issues) |
m (→Known issues) |
||
| Line 10: | Line 10: | ||
* All platforms | * All platforms | ||
** The latest revision of BRAINSTools isn't used. BRAINSWrap module failed to compile with BRAINSDEMONWARP_DEBUG_OUTPUT OFF. Issue reported [https://github.com/BRAINSia/BRAINSStandAlone/issues/13 here]. | ** The latest revision of BRAINSTools isn't used. BRAINSWrap module failed to compile with BRAINSDEMONWARP_DEBUG_OUTPUT OFF. Issue reported [https://github.com/BRAINSia/BRAINSStandAlone/issues/13 here]. | ||
| − | * Linux 64-bit | + | * Linux 64-bit / MacOSX 64-bit |
** BRAINS GTract based modules are not working. Library libGTRACTCommon.so hasn't been packaged. Issue reported [https://github.com/BRAINSia/BRAINSStandAlone/issues/14 here]. | ** BRAINS GTract based modules are not working. Library libGTRACTCommon.so hasn't been packaged. Issue reported [https://github.com/BRAINSia/BRAINSStandAlone/issues/14 here]. | ||
* Windows 32-bit | * Windows 32-bit | ||
Revision as of 23:53, 28 October 2011
Home < Snapshots
 |
This page lists Slicer pre-4.0 packages.
For a complete list of Known issues, please refer to the bug tracker. |
10/28/2011
Known issues
- All platforms
- The latest revision of BRAINSTools isn't used. BRAINSWrap module failed to compile with BRAINSDEMONWARP_DEBUG_OUTPUT OFF. Issue reported here.
- Linux 64-bit / MacOSX 64-bit
- BRAINS GTract based modules are not working. Library libGTRACTCommon.so hasn't been packaged. Issue reported here.
- Windows 32-bit
- There are still "memory leaks", it means that a popup will appear when you will be closing Slicer on windows. We are aware of that issue. The developer that should be fixing these has already being notified in person few days ago. A reminder has been sent on the list.
 |
When we will be releasing the official Slicer 4.0 binaries, the package will be built with "memory leaks reporting" disabled.
In the mean time, it's is important to track these down since they demonstrate a flow in the implementation and could lead to an application using the entire memory of the workstation. |
