Unity game crashes when build but not in editor - error-handling

I'm working on a game. I have 30 levels. I spawn a level and destroy the old level at the end of each level. level 0 till 20 works perfect but after that it crashes when it loads the next level. all the levels are in 1 gameobject array.
If I put level 21 in the first place of the array it still happens, I rebuild the levels, checked my code but I just cant find the problem.
the error is a Access Violation(0xc0000005).
link to my error logs:
Error logs download
I also tried alot of other things, reimporting the project, check all the project settings and shader settings, build in older version of Unity, build on other computer.
Some one please help me, because I don't know what to do anymore.

Related

Changes doesn't reflect on run time (code and design)

Im developing a system using vb2022 its almost done but today the changes I made doesn't reflect on run time.
For example I added a button but when I run the program the button will not show.
Same as the code, i can write code but it doesnt reflect on run time
Plus im trying to change the startup form into form 2 (initial is form 1) but it doesn't reflect.
What should I do? I didn't change anything I just opened the file and write code. But suddenly this happened.
Most likely your build is failing and VS is automatically running the old output. When that happens, VS will prompt you whether to run the old output or not by default, but many people tell VS not to prompt them again without actually reading the dialogue. Use the Build menu to build your project/solution and pay attention to the Output and Error List windows to see whether it failed or not.
It may be that the compilation is succeeding but VS simply can't overwrite the output files because they are locked, which does happen sometimes. In that case, just delete the entire obj and bin folders from your project folder. You may need to close VS to do so. The next time you build, new output will be created and run.
If this happens regularly then you should probably repair VS and, if it continues after that, reinstall.

Compiled Access Program Runs Fine on 7 Computers but Crashes on 3 others

I have written a rather complex application in Microsoft Access. It is split into front end and back end files. To protect my code, I have compiled it and saved it as a runtime .accde file, which I then changed to an .accdr file to ensure it operated as a runtime. I have created two versions of the application: one for those with 32-bit Office installed and one for those with 64-bit office. I have used Inno Setup to package the application, the data file, and other files such as the icon file, the license file, etc., into an installable package, which works just fine.
Among my team of 27 beta testers of this application, so far 6 have downloaded it, and I have tested it on four of my own computers. On seven of these computers, the installation works perfectly and the application runs with no problems.
On the computers of three of my testers, when they try to run it, they get this error message:
The expression On Open you entered as the event property setting produced the following error: Bad file name or number.
* The expression may not result in the name of a macro, the name of a user-defined function, or [Event Procedure].
I'm pretty sure I know where the code is that's causing the problem, but cannot for the life of me figure out why the application crashes on those 2 computers but not on others.
The On Open event I suspect of causing the problem checks the linked tables, gets their connect string, then looks at the path for that string for the back end database. If it does not find it there, the procedure pops up a file selector dialog and instructs the user to find the data file, then it relinks all the tables.
If anyone could point me in the right direction to fixing this problem, I would be extremely grateful.
This is typically caused by a reference labelled as MISSING.
You have two (three) options:
Run the application on the offending machines with a full version of Access that lets you debug the code
Create a small test application that lists and verifies the references you use, and run this on the offending machines
Remove those two customers
Thanks to all the contributors here. Because of these folks and additional online research, the latest answer I can find is this:
This error occurs on a small percentage of computers on which the app is installed, and no one has yet figured out why, what causes it, or how to fix it. The workaround is to install the 2013 version of the Access runtime, as later versions will still cause the problem.
At least one of the offending computers is running the Click-to-Run version of Office. Still gathering information, but that's the status as of now.

The specified procedure could not be found - how to identify?

I'm developing plugins for a program. Whenever I try to load my plugin in that program it crashes with an the specified procedure could not be foundbut nothing more.
Well to have an insight I tracked with Process Monitor (or ProcMon). I set the filter to just print messages for the process of my main program. However that application shows me including the libraries ends (after wandering through PATH) at the right file - i.e. Result: SUCCESS.
So my computer left me pretty clueless, yet refuses to work. Has anyone an idea how identify the missing procedure?
N.B.: Additionally I ran the DependencyWalker which gave me the usual error message because it's deprecated (dependency walker gives me errors on the system that runs correctly) - which could indicate that all dependencies are found.

DisconnectedContext was detected:Exception setting can be set for a project?

When i run one of my vb project i get below warning message.
DisconnectedContext was detected
Message: Context 0x21b448' is disconnected. Releasing the interfaces from the current context (context 0x21b2d8).This may cause corruption or data loss. To avoid this problem, please ensure that all contexts/apartments stay alive until the applicationis completely done with the RuntimeCallableWrappers that represent COM components that liveinside them.
A quick google search gave me result like it can be solved by disabling the exception "disconnectedContext ". So I did in menu->debug->exception, under manage debug assistants deselect disconnectedContext and it solved the problem too.
But this setting is not project wise or visual studio wise. I found like this setting is saved in .suo file.Now I want this setting I made to be available for all users using the project. So how it can be set project wise so that all users using the project will be able to get disconnectedContext setting disabled

Subversion xib merge error

So I don't know all that much about subversion, but I use Versions svn to keep my Xcode projects synced between my laptop and desktop and this is the first issue I've had with it. I did a bunch of work on my laptop while away over the weekend and tried to sync when I got home; however, when I committed the changes from my laptop and updated on my desktop, something weird happened. The project opens up (on my desktop computer) but gives me the following error:
The document "ClassInputViewController.xib" could not be opened. Could not read archive.
along with about 50 merge conflicts on various lines of that xib. upon closer inspection of the files, I saw that 3 new files had been added during the update that weren't in the files from my commit on the laptop: ClassInputViewController.xib.mine, ClassInputViewController.xib.r101 and ClassInputViewController.xib.r102 that Versions says aren't under version control. If I delete these files, the merge conflicts in Xcode disappear but the main "Could not read archive" error still occurs. I know one simple solution to this would be to back up the project on my laptop, delete it from svn and add back in the working files, but I'd like to figure out how to fix this is case it happens again with a bigger project that wouldn't be so easy to do that with. Anyone know what to do in this situation?
oooh, I saw it many times. Best solution - it's just throw away the most unserious changes.