Page MenuHomePhabricator
Create Task
Maniphest T17555

State Machine errors when using the persistence module
Closed, ResolvedPublic
Actions

Description

When the persistence module is loaded (method mitk::PersistenceService::LoadModule();) the mitk workbench is not working any more because of state machine errors.

The render windows and plugin UI stay white and there are plenty of state machine errors on the console:

73.98 core.ia.statemachine ERROR: [type: dummy] Error in mitkStateMachine.cpp: S
tateMachine not initialized with the right temporal information!
73.99 core.ia.statemachine ERROR: [type: dummy] Error in mitkStateMachine.cpp: S
tateMachine not initialized with the right temporal information!
73.99 core.ia.statemachine ERROR: [type: dummy] Error in mitkStateMachine.cpp: S
tateMachine not initialized with the right temporal information!
74.20 core.ia.statemachine ERROR: [type: dummy] Error in mitkStateMachine.cpp: S
tateMachine not initialized with the right temporal information!
74.22 core.ia.statemachine ERROR: [type: dummy] Error in mitkStateMachine.cpp: S
tateMachine not initialized with the right temporal information!
74.24 core.ia.statemachine ERROR: [type: dummy] Error in mitkStateMachine.cpp: S
tateMachine not initialized with the right temporal information!

Related Objects

Event Timeline

franza added projects: MITK, Bugzilla.Mar 19 2014, 4:53 PM
franza added a subscriber: franza.Mar 20 2014, 4:35 PM

The error is caused by the statement

m_PersistenceServiceRegistration = context->RegisterService<mitk::IPersistenceService>(m_PersistenceService, _PersistenceServiceProps);

in file mitkPersistenceActivator.cpp

When commenting out this statement, MITK is working again. But the persistence service does not work since it is not registered.

• git-user added a subscriber: • git-user.Mar 26 2014, 3:09 PM

User franza has pushed new remote branch:

bug-17555-ErrorsPersistenceModule
• fetzer added a subscriber: • fetzer.Apr 11 2014, 3:32 PM

Current release is finished. Resetting target milestone

franza added a comment.Apr 16 2014, 4:18 PM

[d2a132]: Merge branch 'bug-17555-ErrorsPersistenceModule'

Merged commits:

2014-04-16 16:00:31 Alfred Franz [638eb2]
cleaned up, added comments

2014-03-27 14:38:24 Alfred Franz [b047e6]
workaround for the persistence of the IGT plugins (see T16643 for details)

2014-03-26 16:43:40 Alfred Franz [618970]
added command to create directory if it doesn't exist

2014-03-26 16:42:32 Alfred Franz [507052]
added check if rendering manager is instantiated to avoid crashes

2014-03-26 15:08:13 Alfred Franz [47b8c9]
replaced inline implementation by normal implementation to avoid errors

• git-user added a comment.Apr 23 2014, 5:57 PM

User muellerm has pushed new remote branch:

bug-17555-reactivate-autoload-for-persistence-module
franza added a comment.Jun 4 2014, 4:34 PM

Is the last branch (bug-17555-reactivate-autoload-for-persistence-module) already merged?

Is this bug finished or not?

muellerm added a subscriber: muellerm.Jun 4 2014, 5:04 PM

[61579a]: Merge branch 'bug-17555-reactivate-autoload-for-persistence-module'

Merged commits:

2014-06-04 15:30:42 Michael Mueller [1c1fac]
fixed error with relative filenames

2014-06-04 15:10:02 Michael Mueller [3c70ef]
corrected dir separators
corrected int initialization in igttrackingdevice
in persistence service: delayed scene io instatiation, enforced creation of data directory if not existent, added error checking
removed static vars in xml file writer and reader

2014-04-23 17:55:51 Michael Mueller [573c56]
reactivated AUTOLOAD_WITH MitkCore for Persistence. seems to work. needs to be tested though...

muellerm added a comment.Oct 16 2014, 11:18 AM

was fixed. for new bugs of the persistence module new tickets should be opened

MITK · MIC · IMSY · DKFZ