Weird stuff that makes gzdoom builder crash

[CyberDestroyer]

Not too much of a question but i've ran into this thing quite a few times.

 

I cant reproduce it but there's this crash and i think it happens when:

• when i move my cursor when making a linedef too fast (rare)
• when i move my cursor really fast after making a linedef
• complex shapes with a lot of line defs (most of the time they are overlapping)

 

This is from memory of yesterday so i might not be 100% accurate on how to do it.

Just wanted to share this with everyone.

[Kappes Buur]

Is there no crash report which you could upload?

 

If that still happens with GZDoom Builder Bugfix then I would assume

that there is something wrong with how your computer is set up.

Edited September 8, 2020 by Kappes Buur

[CyberDestroyer]

6 minutes ago, Kappes Buur said:

Is there no crash report which you could upload?

 

If that still happens with GZDoom Builder Bugfix then I would assume

that there is something wrong with how your computer is set up.

Where would i find a crash report? 

[Kappes Buur]

Normally a screen would pop up with the crash info.

 

However, if it is a 'silent' crash you may find a crash log file in

C:\Users\computername\AppData\Local\Doom Builder

[TheEvilGrin]

Also happens in Doom Builder 2 and Doom Builder X. Never been fixed. Just save every 10 seconds.

[CyberDestroyer]

GZCrash.zip

This was after a crash and i had opened it again, so idk if its much use.

The past crash had a pop up, dismissed it and closed out.

Opening the map again showed a "In your last session something went terribly wrong!"

Continuing, then a silent crash.

 

I tried opening it in doom builder 2 (yeah i use it occasionally)

No crashes, then opening it in gzdoom builder worked.

 

Weird.

[Kappes Buur]

ERROR:
Builder: Attempted to read or write protected memory.
This is often an indication that other memory is corrupt.

 

Just a quick question:

Where on your computer did you install the editor?

I mean the exact location, Drive:/Folder

Edited September 8, 2020 by Kappes Buur

[CyberDestroyer]

31 minutes ago, Kappes Buur said:

ERROR:
Builder: Attempted to read or write protected memory.
This is often an indication that other memory is corrupt.

 

Just a quick question:

Where on your computer did you install the editor?

I mean the exact location, Drive:/Folder

C:\Users\Doompostal\Documents\GZDoom_Builder-r2787

[Kappes Buur]

1 hour ago, CyberDestroyer said:

C:\Users\Doompostal\Documents\GZDoom_Builder-r2787

 

As a first stab at this:

Try to install the editor into another directory, which does not belong to the Windows realm,

something like C:/Editors/GZDBr2787. If you have another drive partition, install in there.

 

I myself have a separate drive dedicated only for DOOM stuff. And every version is grouped

in its own directory and subdirectory. I never install a new version over an old one.

 

Consider this, GZDB ended with r2787, GZDBBugfix ended with r3107, which means that

there are were 320 improvements/bugfixes. And the GUI is identical.

 

Both editors are the same program, except that ZZYZX gave the editor a new name after

he became disenchanted with MaxED's efforts and programmed his own branch, and MaxED

decided to stop his contributions.

 

 

Edited September 8, 2020 by Kappes Buur

[CyberDestroyer]

On 9/8/2020 at 2:58 PM, Kappes Buur said:

 

As a first stab at this:

Try to install the editor into another directory, which does not belong to the Windows realm,

something like C:/Editors/GZDBr2787. If you have another drive partition, install in there.

 

I myself have a separate drive dedicated only for DOOM stuff. And every version is grouped

in its own directory and subdirectory. I never install a new version over an old one.

 

Consider this, GZDB ended with r2787, GZDBBugfix ended with r3107, which means that

there are were 320 improvements/bugfixes. And the GUI is identical.

 

Both editors are the same program, except that ZZYZX gave the editor a new name after

he became disenchanted with MaxED's efforts and programmed his own branch, and MaxED

decided to stop his contributions.

 

 

Ok, thanks!