Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
OpenWalnut Core OpenWalnut Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 86
    • Issues 86
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenWalnut
  • OpenWalnut CoreOpenWalnut Core
  • Issues
  • #217

Closed
Open
Created May 08, 2017 by Johannes Waschke@JohannesDeveloper

-RM-206-MR-Crash of Colormapper

I use the Colormapper as output for a module which creates many datasets per second (that means, the output data of this module changes often). This constantly leads to crashes of OpenWalnut. I guess it is the Colormapper's fault because using (e.g.) Isosurface avoids this problem.

My first thoughts were that it could be a memory issue on the graphics card (the memory is nearly used completely by another module) but I could reproduce the crash even with an "empty" graphics card's memory.

Maybe the fast change of Colormapper's input data could be the reason?

(System: Ubuntu 12.04 64bit, GeForce 9800 GT/PCIe/SSE2, AMD Phenom(tm) II X4 920 Processor × 4 )

Output:

*DEBUG   [WDataTexture3D] Creating Texture of type W_DT_DOUBLE 
*DEBUG   [WDataTexture3D] Resolution: 160x200x160 
*DEBUG   [WDataTexture3D] Channels: 1 
*DEBUG   [WDataTexture3D] Value Range: [0,28299] - Scaler: 28299 
Exception thrown! Callstack's backtrace:
trace: WException::WException(std::string const&)	->	lib/libopenwalnut.so.1(_ZN10WExceptionC2ERKSs+0x11d) [0x7faac9e3d89d]
trace: WSegmentationFault::WSegmentationFault(std::string const&)	->	lib/libopenwalnut.so.1(_ZN18WSegmentationFaultC2ERKSs+0xd) [0x7faac9e2e9ed]
trace: SignalTranslator::SingletonTranslator::SignalHandler(int)	->	lib/libopenwalnut.so.1(_ZN16SignalTranslatorI18WSegmentationFaultE19SingletonTranslator13SignalHandlerEi+0x66) [0x7faac9e2f036]
trace: ()	->	/lib/x86_64-linux-gnu/libc.so.6(+0x364c0) [0x7faac3cc34c0]
trace: ??? 	->	[0x7faa84000248]

terminate called after throwing an instance of 'WSegmentationFault'
  what():  Segmentation Fault.
Aborted (core dumped)

How to reproduce:

  • checkout toolbox from openwalnut.org//srv/hg/ow-probtracking
  • compile toolbox and start ow
  • load symmetric tensor dataset and apply eigensystem module
  • connect evec_1 through evec_3 as well as evals to the probtracking module
  • attach colormapper to this module
  • attach navigation slices module to see something (I think this is not mandantory)
  • Fast move position of the seed point
  • You should see a crash then sometime

(from redmine: created on 2012-08-27, closed on 2013-03-27)

Assignee
Assign to
OpenWalnut 1.4
Milestone
OpenWalnut 1.4
Assign milestone
Time tracking