Author Topic: Fatal Assertion Error  (Read 8734 times)

Offline lukekivi

  • Single posting newcomer
  • *
  • Posts: 3
Fatal Assertion Error
« on: January 23, 2020, 03:25:01 am »
Today I opened my laptop and Codeblocks was open but not visible. I closed it and this error message appeared:


"Fatal Assertion Error

Assertion failed in static MgrT* Mgr<MgrT>::Get() [with MgrT = ProjectManager] at C:\CB17xx\src\include\manager.h:206.

false && "Calling Get after the subsystem has been shutdown is an error!""


Every time I open with the app icon no window ever appears even though it shows the app is running. However, I got the app to start and a window to appear again via the launcher. None of my personal settings work when I start with the launcher. (ex. downloaded themes) It still displays the same error message whenever I close the app.
 
I restarted my computer and reinstalled the app twice.

Offline stahta01

  • Lives here!
  • ****
  • Posts: 7582
    • My Best Post
Re: Fatal Assertion Error
« Reply #1 on: January 23, 2020, 03:44:05 am »
Stop using the Cblauncher; does it then work?

Tim S.
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 64 bit.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline lukekivi

  • Single posting newcomer
  • *
  • Posts: 3
Re: Fatal Assertion Error
« Reply #2 on: January 23, 2020, 04:02:00 am »
Stop using the Cblauncher; does it then work?

Tim S.

I only resorted to the CBLauncher because I need to write code. The CodeBlocks app opens but no window appears. Even so, their shouldn't be an error message every time I close the app.

Offline stahta01

  • Lives here!
  • ****
  • Posts: 7582
    • My Best Post
Re: Fatal Assertion Error
« Reply #3 on: January 23, 2020, 04:16:05 am »
Try copying the CB default config file "default.conf" to a new name (with CB Closed).

Edit: You need to delete the "default.conf"; a new one should be created with CB is ran.

On windows, the default config is in CodeBlocks subfolder under %APPDATA%

Then, start CB normally!

Tim S.
« Last Edit: January 23, 2020, 04:27:15 am by stahta01 »
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 64 bit.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline lukekivi

  • Single posting newcomer
  • *
  • Posts: 3
Re: Fatal Assertion Error
« Reply #4 on: January 23, 2020, 05:43:03 am »
Try copying the CB default config file "default.conf" to a new name (with CB Closed).

Edit: You need to delete the "default.conf"; a new one should be created with CB is ran.

On windows, the default config is in CodeBlocks subfolder under %APPDATA%

Then, start CB normally!

Tim S.

Beautiful! That worked but I am still getting the closing error  :o

Thanks tho!

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: Fatal Assertion Error
« Reply #5 on: January 23, 2020, 08:32:22 am »
Which version of CB and which OS? Do you have some setting changed?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Kanagaraj

  • Guest
Re: Fatal Assertion Error (Solution)
« Reply #6 on: February 19, 2021, 08:00:00 am »
Dear All,

When you try to open codeBlocks and if you get error as "assesrtion failed" in any version do the following procedure to get it solved.

My error: Image Attached.


Solution.

1. Go to Run > type > %appdata%

2. Find the folder named CodeBlocks> Delete this folder

3. Re launch the CodeBlocks application. You will be prompted to select the compiler.

4. Go to setting > toolschains executables > choose compiler > and locate the MinGW folder that you have.

5. Close the CodeBlocks and it asks to save the enviroment and Save it.

6. Relaunch the CodeBlocks. you won't see the error now.

 :) :)


« Last Edit: February 19, 2021, 08:16:38 am by Kanagaraj »

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: Fatal Assertion Error
« Reply #7 on: February 19, 2021, 10:40:57 am »
It would have been better if you've reported the problem properly.

OS, CB version? In this case providing the old config file or a diff might have been helpful. :)
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]