Mod Archive Forums
Music Production => MilkyTracker => Tracking => MilkyTracker Support => Topic started by: fuzion_mixer on October 14, 2017, 10:48:27
-
- Was working on my newest project. Had 2 tabs (one being the project, the other "After the Rain" (https://modarchive.org/index.php?request=view_by_moduleid&query=53).
- When I clicked save, the whole application 'unexpectedly closed'.
- Went back and open the saved file, and the instruments weren't there. Only thing that remained were the patterns. Even then, Patterns C to 16 were corrupted.
Realised this all after adding most of the instruments. Here's a link to download the file.
https://drive.google.com/file/d/0B6Cbq4OCgJxhLUdHbUZyRXQtY1U/view?usp=sharing (https://drive.google.com/file/d/0B6Cbq4OCgJxhLUdHbUZyRXQtY1U/view?usp=sharing)
-
It's hard to guess what has happened without a core dump / memory dump and more details, or what the file looked like before the crash.
Given that it crashed in the middle of saving patterns, there was probably some very specific pattern data that caused this crash. Did you import the file from a format other than XM, maybe?
-
Did you import the file from a format other than XM, maybe?
No I didn't. But I suspect that the crash has something to do with the channel limit. It crashed on me successfully if I loaded a module with </= 32 channels and try to load another with >32 channels.
Interpolation: No interpolation
Sound Driver: Built-in Output
-
Both aftrrain.xm and the_island.xm appear to be <= 32 channels though? Or did the_island.xm use more channels before the crash?
Given that the pattern data becomes misaligned in pattern 12, it would seem realistic if there was a note on channel 32+ there before the crash. But just having a 32+ channels module and one with less channels open and trying to save it is not crashing the tracker here.
-
Or did the_island.xm use more channels before the crash?
Nope, I've never set it to >32 before.
But just having a 32+ channels module and one with less channels open and trying to save it is not crashing the tracker here.
I've tested loading a module with >32 channels, then loading another with <=32. First try, and it crashed, but subsequently it didn't.
Tested the_island.xm with da-eternity.xm (https://modarchive.org/index.php?request=view_by_moduleid&query=35659 (https://modarchive.org/index.php?request=view_by_moduleid&query=35659)) and the first two times it crashed on me, but subsequently it didn't. Both are <=32 channels, too.
But the thing I don't understand is why did it crash when I'm saving my module? All the above results in instant crashes upon loading a second module.
I feel that there is a specific circumstance where even if both modules are within 32 channels and I save, it would crash. I'm yet to figure out what is it exactly. It seems to just crash whenever it feels like it (at least to me).
-
But the thing I don't understand is why did it crash when I'm saving my module? All the above results in instant crashes upon loading a second module.
I think I've tested and figured it out.
If you were to load another module with <= 32 channels and play it for a few seconds, then remove the tab, the application will crash upon any button clicked on the menu. In some cases, it will crash upon removing the tab. However, upon multiple attempts, this being the issue is not confirmed as it did not happen for all the attempts.
-
Which operating system are you on? If you have a way to reproduce the problem, having a coredump/memory dump might possibly make debugging the issue easier.
-
Mac OSX
Regarding the core/memory dump...I don't know what that means or what I should do to retrieve it.
-
In that case some of the actual MT developers who are on OSX may be able to give better instructions... :)
-
I've just had a few attempts to replicate this crash on OSX, loading aftrrain.xm in the first tab then da-eternity.xm in the second - but with no luck.
Can you please provide exact steps to replicate the crash?
Also, please confirm you are using v1.01.
-
Mac OSX
Regarding the core/memory dump...I don't know what that means or what I should do to retrieve it.
are you using high sierra?