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

inconsistent behavior (crash) when state is lost due to code change #7

Open
thefasquelle opened this issue Jul 29, 2024 · 1 comment

Comments

@thefasquelle
Copy link

Some code changes such as adding members to a module will reset project.
Sometime the callback is called and sometime it is not, it seems pretty random.
When it is called, sometime Excel crashes and sometime it doesn't. Also seems pretty random.

Also the crash is not the same depending on init method.
If callback is InitByAddress, Excel freezes briefly then exit with ExitCode = 4 and restart.
If callback is InitByName, Excel becomes unresponsive and just hangs forever (will I never waited more than 5 minutes tbh).

I believe this different behavior depending on init type is the same when application crash at exit so might be related to #3 ?

@thefasquelle thefasquelle changed the title inconsistent behavior (crash) when state is loss due to code change inconsistent behavior (crash) when state is lost due to code change Jul 29, 2024
@cristianbuse
Copy link
Owner

Thanks @thefasquelle ,

There are quite a few issues raised lately. I am planning to work on this class in the next few weeks as currently am too busy. Not sure I will be able to find workarounds for some of these issues though.

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