Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bad allocation #52

Closed
Toilal opened this issue Oct 2, 2017 · 2 comments
Closed

Bad allocation #52

Toilal opened this issue Oct 2, 2017 · 2 comments

Comments

@Toilal
Copy link
Contributor

Toilal commented Oct 2, 2017 •
edited
Loading

After setting up visual studio debuger and enhanced error message handling with #51, I can now help to diagnose crashes we experience in my dev team.

It throws an exception with message Bad allocation after a while.

When I debug, it fails to create a new char array in FileTree GetNodeFullPath method.
@Toilal Toilal mentioned this issue Oct 3, 2017
Merged
@Toilal
Copy link
Contributor Author

Toilal commented Nov 13, 2017

So this one in fixed with the merge, thanks.

@Toilal Toilal closed this as completed Nov 13, 2017
@marcharding
Copy link
Member

I also published the new gem. Thanks for your work on this 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@marcharding @Toilal