(04-24-2014, 12:20 PM)SeannyM Wrote:(04-24-2014, 11:57 AM)zxcvbad Wrote:(04-22-2014, 03:43 AM)SeannyM Wrote:Got some additional info regarding fastmem, that's a Qualcomm bug, It fails to grab 1GB of virtual RAM periodically. Stock dc3 process and bt share process as well as lw was linked to this. Mali shouldn't have problems with fastmem(04-22-2014, 03:37 AM)zxcvbad Wrote: SeannyM, just tested, I believe those problems I'm experiencing are linked to fastmem + bt. Hardware keys just not responding or freeze if I'm running any game with fastmem on. At some point I've got "bt share process crash" system report, that could be fastmem uses RAM till all the other process got terminated, including Sony's dc3 native app (even gamepad turns lights off), few times live wallpaper was turned off. Without fastmem all worked fine, thanks for fixing L/R :-)
Well it does say "unsafe memory optimizations", so it makes sense. I get freezes and crashes with fastmem too, one of the places I get them consistently is loading save states, it usually locks up after loading two states in a row. With fastmem disabled Dolphin is definitely more stable.
Damn. Why does qualcomm have to have such bad drivers for dolphin? Why couldn't mali be the glitchy ones? lol
Mali is also suffering from glBufferSubData/glMapBufferRange stall driver which highly affects performance. Hopefully they've fixed it on r40, no devices uses it at the moment except tv dongle by Rockchip which was spotted at gfxbench