[Build 3124] Crashed while saving my `sublime-syntax` modifications

[evandrocoan]

[Build 3124] Crashed while saving my sublime-syntax modifications

May be related to: https://forum.sublimetext.com/t/st3-crashes-frequently-since-build-3124/23042

Summary

I just added a new scope for the my syntax-file, and ST suddenly closed and generated a dump file. This is the dump file '0d908c15-4582-4b56-a509-d6d38b9b873f.dmp': 0d908c15-4582-4b56-a509-d6d38b9b873f.zip

Expected behavior

Is expected to ST do not crash when saving my changes to a sublime-syntax file.

Actual behavior

The ST is crashing when saving my changes for a sublime-syntax file.

Steps to reproduce

1. Open a syntax file.
2. Add a new scope/context and save the file.
3. ST luckily it will crash and generate a crash report, misfortunately it will not crash.

Environment

• Operating system and version:
  • Windows 10
  • Mac OS ...
  • Linux ...
• Sublime Text:
  • Build 3124 portable located on: D:\User\Applications\SoftwareVersioning\SublimeText

Update

I think it is not related to syntax files, but not something else unpredictable as some third part Installed Package doing something with the API causing the crash, as I experienced other unrelated crashes with the syntax files editing. Like more eight times since this initial report on Sep 22.

What I do after the crash is simply open sublime again. I do not remember about data loss or changes to my work spaces, except the undo command history lost.

[wbond]

Can you provide the changes to made that caused the crash?

[evandrocoan]

These were the changes: full_file_with_diff_changes.zip, this is the commit: evandrocoan/AmxxPawn@6df860f

Note:

At the time, my workspace was very big like within 1000 files for indexing, involving C++ files and AmxxPawn.

[wbond]

Ok, I'll look into it when I get a chance

[evandrocoan]

I never got it happening anymore, closing it for now.

[evandrocoan]

Just crashed again, this is the new dump file: bd38c8a4-b452-499e-a0a2-407df878fc48.zip

1. Like the fist time, now I was saving a code file, not a syntax file. But the import is, the only related event is the saving process.
   • It is important to mention, some times I save the file every minute, other times, each 10 seconds. So, on my day use, there are a lot of saving. I always use ctrl+s for saving.
2. This time, and like the last, the windows Event View did not registered the crash, but Sublime Text created the above dump file.
3. When I was using the build 3114, it had crashed some times, but I do not recall whether it was related to the saving process as it is now.

New dump file/crash on: 13/10/2016

This time I had saved a syntax file change. Was this:

Packages\amxmodx\AMXX-Pawn.sublime-syntax
103:         - match: \n

To this:

Packages\amxmodx\AMXX-Pawn.sublime-syntax
103:         - match: $

3c0ebcee-8b86-466f-a432-3d03ff2c989c.zip

[deathaxe]

I never experienced crashes, when working with syntax-files, but I can confirm there is something wrong with how sublime text handles changes to them.

When changing saving syntax files several times, ...

1. sublime's memory usage increases from 30MB to about (300...400MB).
2. you'll find several files like .5340.tmp in the cache directory of the syntax package.

[evandrocoan]

I think it is not related to syntax files, but not something else unpredictable. I experienced other crashes like more five since this initial report on Sep 22.

What I do after the crash is simply open sublime again. I do not remember about data loss or changes to my work spaces.

However, this other bug report changes as always happens after a program restart or project change:

1. Restore session, does not set the last scroll position after a project change, or sublime restart #1379 _ Restore session, does not set the last scrool position after a project change, or sublime restart

I also got tired about post the dump file here. The Sublime Crash reporter should be updating them correctly as it always lunch after the crash.