Bug #97248 .Net Driver consume huge memory when connection timeout

Submitted: 16 Oct 2019 7:46 Modified: 5 Jun 2020 13:38
Reporter: ybb huang Email Updates:
Status: No Feedback Impact on me:
None 
Category:Connector / NET Severity:S2 (Serious)
Version:6.9.10 OS:Any (centos7)
Assigned to: CPU Architecture:Any (x86_64)
Tags: Memory, NextResult, timeout

File: Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

  • On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
  • On windows use WinZip or a similar utility to split the large file
[16 Oct 2019 7:47] ybb huang
stack

Attachment: callstack.png (image/png, text), 100.63 KiB.

[16 Oct 2019 7:52] ybb huang
number of columns

Attachment: numCols.png (image/png, text), 37.51 KiB.

[16 Oct 2019 8:18] ybb huang
problem description

Attachment: stack explain.jpg (image/jpeg, text), 57.38 KiB.

[16 Oct 2019 8:19] ybb huang
suggestion

Attachment: suggestion.png (image/png, text), 417.66 KiB.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.039 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.