Skip to content

Thread safety of deserialized objects #383

@JohnEmhoff

Description

@JohnEmhoff

Is it expected that a message deserialized from a pipe in thread 1 can be passed and safely read from thread 2? I'm running into an issue where attempting to inspect such an object hangs when accessed from thread 2. It only seems to happen when the object is ~64k or greater.

My workaround for now is to instead call .to_dict() on the message and pass that around instead, which works but is obviously not great.

If this is surprising behavior I can put together a reproduction.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions