LivelyKernel / LivelyKernel/lively.morphic
inspector opened on a morph break serialization of entire world
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
```
Error saving world: Error: Error snapshotting morph: Cannot recreate morph from snapshot!
TypeError: Illegal constructor
at ClassHelper_restoreIfClassInstance_ (https://lively-next.org/lively.serializer2/class-helper.js:94:56)
at ClassPlugin_deserializeObject_ (https://lively-next.org/lively.serializer2/plugins.js:96:39)
at ObjectPool_plugin_deserializeObject_ (https://lively-next.org/lively.serializer2/object-pool.js:325:71)
at ObjectRef_recreateObjFromSnapshot_ (https://lively-next.org/lively.serializer2/object-pool.js:528:29)
at Function.ObjectRef_fromSnapshot_ (https://lively-next.org/lively.serializer2/object-pool.js:592:47)
at ObjectPool_readSnapshot_ (https://lively-next.org/lively.serializer2/object-pool.js:232:45)
at ObjectPool_resolveFromSnapshotAndId_ (https://lively-next.org/lively.serializer2/object-pool.js:245:20)
at Window.deserialize (https://lively-next.org/lively.serializer2/index.js:50:20)
at step2 (https://lively-next.org/lively.serializer2/index.js:60:42)
at
at Window.createMorphSnapshot (https://lively-next.org/lively.morphic/serialization.js:114:15)
at
```
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at lively.morphic/serialization.js:114, where createMorphSnapshot leads into lively.serializer2/index.js and the stack reaches class-helper.js:94. Reproduce saving a world with the inspector open, then trace the Illegal constructor through plugins.js and object-pool.js. Done means the world saves without the snapshotting or morph recreation error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100