Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.

Colorizer causes A/V on IDE shutdown, trapped by madExcept #25

Open
ByteJuggler opened this issue Oct 14, 2016 · 5 comments
Open

Colorizer causes A/V on IDE shutdown, trapped by madExcept #25

ByteJuggler opened this issue Oct 14, 2016 · 5 comments

Comments

@ByteJuggler
Copy link

ByteJuggler commented Oct 14, 2016

Since Delphi Seattle IIRC there's been some kind of pointer/reference issue in DITE that often causes an A/V on IDE shutdown. I went through the entire Seattle release without DITE because of this irritation and reinstalled recently as we've upgraded to Berlin, but I'm now having the same crash still in both Berlin and Seattle. It gets caught and raised by madexcept, as shown here:

ijqo7si

(Needless to say, this does not happen when the IDE colorizer is not installed. (Edit It may be the case that this AV is not be visible when madExcept is not installed, as this is in the final shutdown of the IDE and thus exposed by madExcept's IDE Exception handling. I've not gone to the trouble of actually uninstalling madExcept to check this yet.)

@RRUZ
Copy link
Owner

RRUZ commented Oct 14, 2016

Hi, Thanks for report this, I use Delphi Berlin and madexcept too, but not AV was raised when the plugin is running, Can you please include the full madexcept report. because there is not reference to the plugin in the image.

@ByteJuggler
Copy link
Author

OK, I'll get back to you. I suppose It's also possible that there's something else going on and that the plugin isn't the cause but nevertheless is the catalyst for whatever problem is happening to be triggered. Thanks for the speedy response. (If I find some time I might go and rebuild/reinstall step by step to see if I can pinpoint where things go pear shaped exactly...)

@ByteJuggler
Copy link
Author

ByteJuggler commented Oct 20, 2016

Hi. here is 2 crash reports from 2 different pc's. One was running Seattle, the other Berlin. The error does not happen every time unfortunately, though typically after having done some things. I will attempt to post steps to reproduce this if I can nail it down. Unfortunately this feels like some kind of pointer reference problem so may be quite hard to track down as the actual problem is likely not close to where it breaks. It also means the issue might not be due to a bug in the colorizer. (However the problem does not occur, at all, unless the colorizer is installed.)
bugreport_pc1_berlin.txt
bugreport_pc2_seattle.txt

@RRUZ
Copy link
Owner

RRUZ commented Oct 20, 2016

Thanks for the additional info.

@tSlappy
Copy link

tSlappy commented Sep 17, 2017

Maybe this AV is connected to this:
image

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

No branches or pull requests

3 participants