RealPlayer 14.0.3.647

RealNetworks Inc - (Freeware)

Real Player is a program specially designed for video playback although it also contains many other useful and interesting features.

Real Player is a software program that includes the latest media player, music jukebox and listen to most common formats on the Web browser integrated multimedia.

The suite includes a multi-channel audio player, with the ability to create playlists, etc.

RealPlayerâ€™s interface is pretty close to the Windows Media Player with 5 tabs available at the top of the screen, being very intuitive and easy to use. As the user quickly understood it, the first section will be the one in which it will find the media being played (either local media or online).

The library proved completely standard at the first use, it will ask the software to scan the directories to add songs to it. RealPlayer will especially look for album art on the internet. The burning functionality is supported through the library.

With this software it is also possible to download videos on specialized sites, format conversion of files and more.

It is also possible to convert a file from one format to another as long as user has the proper codecs. Real Player is capable of transferring video files to devices such as iPods, game consoles and other devices of its kind.

In case the user wants to raise or collect several videos, it offers all the necessary tools for this. Once the installation is finished , the user can share the video on social networks or on specialized sites for streaming video online.

Title:: RealPlayer 14.0.3.647
File Size:: 24.6 MB
Requirements:: Windows XP / Vista / Windows7 / XP64 / Vista64 / Windows7 64 / Windows8 / Windows8 64
Language:: en-us
License:: Freeware
Date Added:: 12 Apr 2011
Publisher:: RealNetworks Inc
Homepage:: http://www.real.com
MD5 Checksum:: 61677B799FD0A7DB5090D47FA66029EB

# Bugs Fixed
- Important Change; Replication: When the server was running with --binlog-ignore-db and SELECT DATABASE() returned NULL (that is, there was no currently selected database), statements using fully qualified table names in dbname.tblname format were not written to the binary log. This was because the lack of a currently selected database in such cases was treated as a match for any possible ignore option rather than for no such option; this meant that these statements were always ignored. Now, if there is no current database, a statement using fully qualified table names is always written to the binary log.
- InnoDB: Valgrind testing returned memory leak errors which resulted from a regression . The dict_create_add_foreign_to_dictionary function would call pars_info_create but failed to call pars_info_free.
- InnoDB: The fix for resulted in a linker error.
- InnoDB: Crash recovery would fail with a !recv_no_log_write assertion when reading a page.
- Replication: Using the --replicate-* options (see Replication Slave Options and Variables) could in some cases lead to a memory leak on the slave.
- Replication: The binary log contents got corrupted sometimes, because the function MYSQL_BIN_LOG::write_cache always thought it had reached the end-of-cache when the function my_b_fill() reported a '0,' while that could also mean an error had occurred. This fix makes sure that whenever my_b_fill() returns a '0,' an error check is performed on info->error.
- The WKB reader for spatial operations could fail and cause a server exit.
- A GROUP_CONCAT() invocation containing subquery having an outer reference caused the server to exit.
- For debug builds, GROUP_CONCAT(... ORDER BY) within an ORDER BY clause could cause a server exit.
- If loose index scan was used on a query that used MIN(), a segmentation fault could occur.
- A prepared statement that used GROUP_CONCAT() and an ORDER BY clause that named multiple columns could cause the server to exit.
- ORDER BY MATCH ... AGAINST could cause a server exit.
- When a partition is missing, code in ha_innodb.cc would retry 10 times and sleep for a microsecond each time while holding LOCK_open. The retry logic for partitioned tables was introduced as a fix but did not include a test case to validate it. This fix removes the retry logic for partitioned tables. If the problem reported reappears, a different solution will be explored.
- The mysql.server script exited with an error if the status command was executed with multiple servers running.
- When processing row-based-replication events in the old binary log format from prior to MySQL 5.1 GA builds, mysqlbinlog could result in out-of-bounds heap buffer reads and undefined behaviour.
- The mysql client allocated but did not free a string after reading each line in interactive mode, resulting in a memory leak.
- Grouping by an outer BLOB column in a subquery caused a server exit.
- The url columns in the mysql datatbase help tables were too short to hold some of the URLs in the help content. For new installations, these columns are now created as type TEXT to accommodate longer URLs.
- For upgrades, mysql_upgrade does not update the columns. Modify them manually using these statements:
ALTER TABLE mysql.help_category MODIFY url TEXT NOT NULL;
ALTER TABLE mysql.help_topic MODIFY url TEXT NOT NULL;
- The test for stack overrun did not work for recent gcc versions and could lead to server exit.
- IF() function evaluations could produce different results when executed in a prepared versus nonprepared statement.