Accordance Enthusiast Posted September 21 Share Posted September 21 Basically what happened is I had a workspace open which should have opened a specific module. But that module was not installed. So after installing, the workspace still opened empty, and when I clicked on that empty workspace it crashed. Accordance 14.0.7 (14.0.7.0) Windows 10 (10.0.19045) RAM: 1024MB free of 8101MB total Disc: 69GB free of 237GB total Exception Description: EAccessViolation: Access violation Exception Thread: 12052: Main Thread Exception Backtrace: $0086AEAB $008C281B $008C1B7A $008FBA16 $008FDC14 $008FCC43 $008FBE6A $008FD08F $008FCDDD $008FBE6A $008FE990 $008F6297 $008F5F40 $00555C4E $008071A9 $0083DC5C $00811849 Link to comment Share on other sites More sharing options...
Nathan Parker Posted September 21 Share Posted September 21 Do you know what module was supposed to open? Is that a module you own and just didn't have installed or don't own at all? Link to comment Share on other sites More sharing options...
Accordance Enthusiast Posted September 21 Author Share Posted September 21 4 hours ago, Nathan Parker said: Do you know what module was supposed to open? Is that a module you own and just didn't have installed or don't own at all? It was the Mishnah add on, which I uninstalled and then re-installed. Not sure if that is the issue or if it will happen with similar modules too. Link to comment Share on other sites More sharing options...
Nathan Parker Posted September 22 Share Posted September 22 OK keep us posted. Link to comment Share on other sites More sharing options...
robrecht Posted October 9 Share Posted October 9 @Nathan Parker Link to comment Share on other sites More sharing options...
.png.c3123c857d1029f98e39c9394adc358d.png)
.thumb.png.4dd247c22789954e2b3cca0d24bf0738.png)
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now