Comments (1)
From [email protected] on March 08, 2011 16:37:04
Kryo serializers write to a ByteBuffer directly. When the buffer is overrun, it throws an exception which unrolls the stack all the way back to the ObjectBuffer, where the buffer size is doubled. At this point, there is no way to resume serialization where the overrun occurred, so serialization has to start from the beginning. The only thing that will really help is to use a larger initial buffer size.
The solution to this is to have Kryo not use ByteBuffer directly, but to use a Kryo specific buffer class. This would allow the buffer to grow without copying and without interrupting serialization (by keeping a list of buffers and allocating new ones as needed). It would also allow more flexibility when dealing with streams. I've collected a number of ideas for a rewrite of Kryo, but don't currently have a timeline.
Status: WontFix
from kryo.
Related Issues (20)
- Redisson 3.24.3 java.lang.NoClassDefFoundError: com/esotericsoftware/kryo/serializers/DefaultSerializers$UUIDSerializer HOT 2
- Spring microservice encounters infinite loop when calling readLongs method resulting in denied access. HOT 3
- Could not serialize Lambda. If anyone knows this, then please response. HOT 6
- Compatibility issue between 5.5.0 and 5.6.0 HOT 2
- failed to lazily initialize a collection, no session or session was closed while trying to deserialize SPRING_SECURITY_CONTEXT HOT 3
- Add GregorianCalendar default serializer HOT 1
- Maven artifact not found HOT 4
- Encountered ArrayIndexOutOfBoundsException when running in Apache Spark 3.3.1 HOT 3
- Allow Kryo instances to be compared using .equals() & .hashcode() HOT 3
- deserialize failure in JDK 21 HOT 5
- When an anonymous inner class is used to initialize a collection, the elements are doubled. HOT 1
- Kryo5 deserialization lost Locale script field HOT 1
- The Input class changes its buffer when deserialize a string HOT 3
- About how to build serializer by custom self-reference class HOT 4
- Cannot run benchmarks HOT 4
- Urgent: Data Corruption Issue Identified During DTO Deserialization (Instance Variable Renamed/Type Changed) HOT 10
- schema validation failed while deserialize data serialized by Encoder.Bean Serializer using Kryo. HOT 2
- Comparison with ObjectInputStream and ObjectOutputStream HOT 2
- How to configure CompatibleFieldSerializer in Kryo3 ? HOT 2
- ExternalizableSerializer does not support circular references HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from kryo.