View Single Post
Old 02-25-11, 04:46 PM   #1
rnissl
Registered User
 
Join Date: Jun 2005
Posts: 36
Default 270.26 and 270.29 cause memory corruption in vmware-vmx (7.1.3) using 3D acceleration

Hi,

this is a sample error message:
Code:
*** glibc detected *** /usr/lib/vmware/bin/vmware-vmx: malloc(): memory corruption: 0x000000000131cfe0 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x73226)[0x7f1e02352226]
/lib64/libc.so.6(+0x75521)[0x7f1e02354521]
/lib64/libc.so.6(__libc_malloc+0x79)[0x7f1e02356aa9]
/usr/lib64/libX11.so.6(_XReply+0xda)[0x7f1e034f8bea]
/usr/lib64/libGL.so.1(+0x78ba3)[0x7f1d3f62eba3]
======= Memory map: ========
It happens at random times (most likely when the Windows 7 x64 login screen appears or when you re-run the assessment in control panel performance information and tools) when the virtual machine is configured to accelerate 3D graphics. I did not see this issue with 260.19.36 and earlier versions.

Bye.
Attached Files
File Type: gz nvidia-bug-report.log.gz (77.2 KB, 69 views)
rnissl is offline   Reply With Quote