[WoW 3.3.5a][Noggit Qt 2017-06-23] Crash on custom map load (SIGSEGV error)

[Scade]

Hey there !

A month ago, I compiled Noggit from its repo and created and edited a custom map. And I didn't do anything else on it since.
Today, after updating Noggit (So log says 3.0, but I'm not sure this is right). I tried to open my map but I got a SIGSEGV error.

Here is the log : https://pastebin.com/b5uf2eZg
Here is the conf file : https://pastebin.com/r2BUwAa8
I couldn't use pastie, it keeps asking me to check a captcha

- I tried to open the map with my 1 month old version of Noggit and it crashes too, so it's more likely due to my files and not Noggit itself.
- If I try to open the map  as far away as possible from adt 27/27, it opens fine, but as soon as I come close enough, it crashes again.
- I tried to open other maps and it works just fine.
- I have no custom patches. The only custom files are the wdt and the adts of the new map, Map.dbc and MapDifficulty.dbc.
- Just to make sure, I copied MPQs from a clean version of WotLK, but the error is still there.
- I commented the "ProjectPath" value, as suggested in another topic but log stays exactly the same.

Thanks for reading, any idea or suggestion is most welcome

[Amaroth]

I won't really help you, but gor just a few notes to say:
1. 3.0 version is never correct. That just means that its Noggit for WotLK. So you've got some version where version number is not correctly shown.

2. Noggit compiled from repo should not be used for any serious work, only for testing. So, if you wanted to test that Noggit, I'd suggest you to send bug report to bitbucket in Issues section. Otherwise I'd suggest you to use version which is proven to work, this may be some random issue which was at one random point present on repo, which may be even already fixed.

3. In either way, devs may want to see ADT which is giving you crashes.

[schlumpf]

4. please reference the exact commit that you built from

5. the .conf file is no longer used, editing it is entirely worthless

6. please build Debug or RelWithDebInfo

7. the log really doesn't look like an issue from loading files

8. please make an issue on the repository (with a log from a debug build, see 6)

thanks