http://bugs.winehq.org/show_bug.cgi?id=55176 --- Comment #8 from Rémi Bernon <rbernon(a)codeweavers.com> --- I don't think it's going to work well, the large block size threshold is dependent on the size representation capacity in the small block header. Also I'm not sure the version check is going to be well received, though arguably this is the right thing to do: changing exposed version is a manual step and it is not very convenient, and this should probably be a per-application compatibility flag somewhere in the future when we have those. What could be acceptable, perhaps in the meantime if some application really depends on this, is simply to get rid of the growable heap restriction, for instance if HEAP_NO_SERIALIZE flag has been used too to make sure it's less likely to break anything, with a FIXME perhaps when the workaround gets triggered. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.