You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We using FB 2.5.7 x32. When I in firebird.conf changing value of parameter LockMemSize from default value 1048576 to "2M" or other, I can't connect to server - when using fbembed.dll, get access violation in dll, when try connect to server - "Error writing data to the connection.". In FB 3.0 using "2M" work without problem.
The text was updated successfully, but these errors were encountered:
With 2 bytes of shared lock memory? Which is less than header size? I'd say crash is almost expected behavior :) Certainly we can add some protection but if we decide to do it protection code should be applied systematically to all .conf files, not only single value.
Based on the comments, it seems this case is "Won't Fix" -- support for K/M/G was only added to v3.x, "protection code" logic for .conf file values is a separate feature request (though related to this issue)
Sean Leyne, I agree with "Won't Fix". Can you create a ticket for implementation protection logic? It will be a little difficult for me to describe it.
Submitted by: Maxim Kuzmin (cybermax)
We using FB 2.5.7 x32. When I in firebird.conf changing value of parameter LockMemSize from default value 1048576 to "2M" or other, I can't connect to server - when using fbembed.dll, get access violation in dll, when try connect to server - "Error writing data to the connection.". In FB 3.0 using "2M" work without problem.
The text was updated successfully, but these errors were encountered: