MySQL Bugs: #38706: MySQL 5.1.25 (Error No 11135) (Out of Memory Error)

Bug #38706	MySQL 5.1.25 (Error No 11135) (Out of Memory Error)
Submitted:	10 Aug 2008 22:14	Modified:	11 Sep 2008 4:41
Reporter:	Viny Ji	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S2 (Serious)
Version:	5.1.25	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
Recently upgraded MySQl version from 5.0 to 5.1.25

After upgrade, application is not able to make more than 300 connection to mysql. With the earlier version system was able to make more than 700 connection.

Please help !

Following variables are used:

binlog_cache_size		:32768
bulk_insert_buffer_size		:8388608
innodb_additional_mem_pool_size		:20971520
innodb_buffer_pool_size		:1073741824
innodb_concurrency_tickets		:500
innodb_lock_wait_timeout		:50
innodb_log_buffer_size		:10485760
innodb_log_file_size		:5242880
innodb_open_files		:300
innodb_thread_concurrency		:8
innodb_thread_sleep_delay		:10000
interactive_timeout		:28800
join_buffer_size		:131072
key_buffer_size		:8388608
key_cache_age_threshold		:300
key_cache_block_size		:1024
key_cache_division_limit		:100
myisam_max_sort_file_size		:107374182400
myisam_sort_buffer_size		:61865984
open_files_limit		:2048
query_alloc_block_size		:8192
query_cache_limit		:1048576
query_cache_min_res_unit		:4096
query_prealloc_size		:8192
range_alloc_block_size		:4096
read_buffer_size		:65536
read_rnd_buffer_size		:262144
sort_buffer_size		:262144
storage_engine		:InnoDB
table_type		:InnoDB
thread_stack		:196608
tmp_table_size		:67108864
transaction_alloc_block_size		:8192
transaction_prealloc_size		:4096
version		:5.1.25-rc-community-log

Error:

Could not connect the specified host.
MySQL Error No 11135
Can't create a new thread(errno 12). If you are not out of memory, you can consult the manual for possible OS-dependent bug.

How to repeat:
Upgrade version from mysql 5 to mysql 5.1.25

Thank you for a problem report. Please, try to repeat with a newer version, 5.1.26, and inform about the results. 

Had you run mysql_upgrade after upgrading from 5.0.x?

Thanks for the quick response.

Yes, I did run mysql_upgrade after the upgrade. I will try 5.1.26.
Is there any existing bug with 5.1.25 because of which you want me to try 5.1.26?
Please let me know.

> Is there any existing bug with 5.1.25 because of which you want me to try 5.1.26?

No, I do not mean any specific bug fixed in 5.1.26. I just want to be sure that the problem is repeatable with a recent version (nobody will fix 5.1.25 anyway), and as there is no repeatable test case presented in this report to check myself I asked you to check it.

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".