Opened 6 years ago
Last modified 6 years ago
#2656 accepted defect
Calling session_save_pointers() on a Collection crashes ChimeraX
| Reported by: | Tristan Croll | Owned by: | Eric Pettersen |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Notify when closed: | Platform: | all | |
| Project: | ChimeraX |
Description
Trying to come to terms with how session save/restore works for Collection instances, since I have a host of classes using the same framework. Anyway, calling:
m = session.models.list()[0] m.atoms.session_save_pointers(session)
... causes a segmentation fault. Presumably because Structure::session_save_setup() hasn't been called yet... but my grep-fu still hasn't found where it actually *does* get called. Anyway, considering that this is a public method it should probably throw an error if called outside the session-save pipeline.
Change History (3)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
| Summary: | Calling session_save_pointers() on a Collection crashes ISOLDE → Calling session_save_pointers() on a Collection crashes ChimeraX |
|---|
Crashes *ChimeraX*. Sorry - not enough caffeine this morning. :)
comment:3 by , 6 years ago
| Priority: | major → minor |
|---|---|
| Status: | assigned → accepted |
Note:
See TracTickets
for help on using tickets.
Ah! Now I see where it gets called...