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

Crash reproduction #11

Closed
JuGGerNaunT opened this issue Apr 23, 2020 · 5 comments · Fixed by #12
Closed

Crash reproduction #11

JuGGerNaunT opened this issue Apr 23, 2020 · 5 comments · Fixed by #12

Comments

@JuGGerNaunT
Copy link
Contributor

I was able to reproduce this crash.

  1. Select tile_land3.gm1 item
  2. Select tile_land8.gm1 item
  3. Once again select tile_land3.gm1 item
  4. Once again select tile_land8.gm1 item
  5. Keep switching between those items. It takes like 10-20 switches until it crash.

It isn't managed .net exception, so there is no callstack. Only this error if I run program under debugger

An unhandled exception of type 'System.AccessViolationException' occurred in SkiaSharp
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
@PodeCaradox
Copy link
Owner

With my fixes for the new release there is no error, cant reproduce it.
Or did you mean select a image from the gm1?

@JuGGerNaunT
Copy link
Contributor Author

JuGGerNaunT commented Apr 23, 2020

Items in the right list. You need to switch items fast enough to reproduce it
It crashes only for tile_land3.gm1 and tile_land8.gm1. Switching between other items work fine.
I checked old version and it also crashes only for those 2 items.

@PodeCaradox
Copy link
Owner

ok in my new version it is not crashing and i clicked so fast on my arrow keys up and down. It buffered the input and showed after i ended clicking the arrows the up and down but no error.

Wait do you get the error only in debug Mode? Or did you test with release. Because i tested release.

@JuGGerNaunT
Copy link
Contributor Author

JuGGerNaunT commented Apr 24, 2020

Or did you test with release. Because i tested release.

it was present in both modes. though in debug mode it was much easier to reproduce it, just with couple of switches. i committed pr, looks like it fix this issue.

@PodeCaradox
Copy link
Owner

ok thanks i merged it

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