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.

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

Read access violation when setting type filters on release #40

Open
naorliron2 opened this issue Feb 28, 2022 · 4 comments
Open

Read access violation when setting type filters on release #40

naorliron2 opened this issue Feb 28, 2022 · 4 comments

Comments

@naorliron2
Copy link

Can't seem to replicate consistently, But when using the file browser I will sometimes get an "Exception thrown at 0x00007FF776436552 in ProjectName.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFF8."

the call stack shows that this is caused by SetTypeFilter().
Capture (2)

Also important to note that this only happens in release

@AirGuanZ
Copy link
Owner

Hi,
The only call to std::vector::clear in SetTypeFilters is at its beginning for clearing old filters, and all accesses to this vector object in other functions are read-only. Therefore the cause of the crash seems to be at another location (which breaks the internal states of typeFilters_).
BTW, you can use data breakpoint to find the code that unexpectedly changes the pointer in the string object.

@naorliron2
Copy link
Author

I tried to use a data breakpoint, but I get an error that the variable was optimized away(might be the issue?). other than that I only have one call to SetTypeFilters() which I followed, and the state of the vector does seem fine

@AirGuanZ
Copy link
Owner

AirGuanZ commented Mar 3, 2022

That makes the problem hard to track. Since the internal state of typeFilters_ may be broken by other memory writes in the program. Sorry for not being able to provide some useful help.

@naorliron2
Copy link
Author

Oh don't worry about it, its not really a big deal on my part, mostly wanted to help this project as much as I can, if you have any more recommendations for debugging I will do some more tests when I have time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants