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
If you do not call "setUser" on the WampConnection and provide a username and password, when the WampConnection attempts to connect, the application crashes because of a memory allocation issue related to WampCraUser in the WampConnectionPrivate class
The primary issue seems to be the odd way that the parent of the WampCraUser class is managed. I believe if you just remove all the special code related to parent and use it as a standard QtObject struct, you remove any issues related to the memory management. I can't understand why the special parent management is necessary.
I have fixed this issue in my fork and will update when I have more information.
The text was updated successfully, but these errors were encountered:
If you do not call "setUser" on the WampConnection and provide a username and password, when the WampConnection attempts to connect, the application crashes because of a memory allocation issue related to WampCraUser in the WampConnectionPrivate class
The primary issue seems to be the odd way that the parent of the WampCraUser class is managed. I believe if you just remove all the special code related to parent and use it as a standard QtObject struct, you remove any issues related to the memory management. I can't understand why the special parent management is necessary.
I have fixed this issue in my fork and will update when I have more information.
The text was updated successfully, but these errors were encountered: