Bug #71082 | mysql client was crashed while loading data | ||
---|---|---|---|
Submitted: | 5 Dec 2013 3:18 | Modified: | 25 Apr 2014 16:44 |
Reporter: | zhai weixiang (OCA) | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Command-line Clients | Severity: | S3 (Non-critical) |
Version: | 5.7.3, 5.5.18 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[5 Dec 2013 3:18]
zhai weixiang
[5 Dec 2013 3:40]
zhai weixiang
some description seems dislocation....just ignore it. ----> (gdb) p (unsigned long long) (str_length + arg_length) $50 = realloc(str_length+arg_length)
[5 Dec 2013 17:24]
liu hickey
Tweak the realloc arg from uint32 to uint64 is not a good choice. I wounder why str_length is so big, that is almost reached (uint32)-1? Keep on appending to the same string? If so, lots of problems, especially performance issues.
[6 Dec 2013 19:58]
Sveta Smirnova
Thank you for the report. Verified as described.
[25 Mar 2014 16:44]
Sveta Smirnova
Zhai, I stopped repeating the crash in my environment and could not find my record about how client exactly crashed. Now I only get "ERROR 2006 (HY000): MySQL server has gone away" messages which is not a bug, because server stops accepting packets from client after its max_allowed_packet reached and closes connection. Please provide output from your environment in time when crash happens.
[26 Apr 2014 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".