Author Topic: Sudden crashes. v3.0.5972 (MB almost never crashed on me).  (Read 5978 times)

peewee678

  • Full Member
  • ***
  • Posts: 143
Sudden crashes. v3.0.5972 (MB almost never crashed on me).

Since yesterday I have had three sudden crashes with the following errors:

11-5-2016 9:47:35 - 6.1.7601.65536 - 3.0.5972.20921 - System.IndexOutOfRangeException: De index ligt buiten de matrixgrenzen.
   bij #=qFVnTf5SxxoEB5tLlkoLvh$hRzxJRr9EaDb7O8UR0MKE=.#=qPlbkma4EyaAamon3FlrJIQ==(Int32 #=q3Pg_1bowvJy2R4F5Y3e9Yw==, String #=qKT54DGjqSCSJ8L8mCzrcBA==, Object #=q3e9ImqnUASgbiPk9wVPTLQ==, Bitmap #=qeuERM22msxfmdCwSDSf2_A==)
   bij #=qFVnTf5SxxoEB5tLlkoLvh$hRzxJRr9EaDb7O8UR0MKE=.#=qMOwvbmE8ZwtIkEyfJaIAAQ==.#=qgdlQc0wiWtpeM8pP44wYqA==(IList`1 #=qpMaxTYSs201wYXGiU5aAlQ==)
   bij #=qFeTrPQ3tnQM_SwIKR1lwKgbkVkUdCZn7pqLCF6ziBDk=.#=qzp2QEhq4Z32Zg3psb_sM80x4CAKpjEKxS6fZJ6xue$s=(#=qMOwvbmE8ZwtIkEyfJaIAAQ== #=qxG$eOmQ_Y4gPymAYJIEn7A==, Boolean #=qxuIfmIG2_oxFdCWzfKdxVzJjy7_AEy_GKuOwoGPTF_Y=)

11-5-2016 10:10:21 - 6.1.7601.65536 - 3.0.5972.20921 - System.IndexOutOfRangeException: De index ligt buiten de matrixgrenzen.
   bij #=qFVnTf5SxxoEB5tLlkoLvh$hRzxJRr9EaDb7O8UR0MKE=.#=qPlbkma4EyaAamon3FlrJIQ==(Int32 #=q3Pg_1bowvJy2R4F5Y3e9Yw==, String #=qKT54DGjqSCSJ8L8mCzrcBA==, Object #=q3e9ImqnUASgbiPk9wVPTLQ==, Bitmap #=qeuERM22msxfmdCwSDSf2_A==)
   bij #=qFVnTf5SxxoEB5tLlkoLvh$hRzxJRr9EaDb7O8UR0MKE=.#=qMOwvbmE8ZwtIkEyfJaIAAQ==.#=qgdlQc0wiWtpeM8pP44wYqA==(IList`1 #=qpMaxTYSs201wYXGiU5aAlQ==)
   bij #=qFeTrPQ3tnQM_SwIKR1lwKgbkVkUdCZn7pqLCF6ziBDk=.#=qzp2QEhq4Z32Zg3psb_sM80x4CAKpjEKxS6fZJ6xue$s=(#=qMOwvbmE8ZwtIkEyfJaIAAQ== #=qxG$eOmQ_Y4gPymAYJIEn7A==, Boolean #=qxuIfmIG2_oxFdCWzfKdxVzJjy7_AEy_GKuOwoGPTF_Y=)

11-5-2016 12:56:34 - 6.1.7601.65536 - 3.0.5972.20921 - System.IndexOutOfRangeException: De index ligt buiten de matrixgrenzen.
   bij #=qFVnTf5SxxoEB5tLlkoLvh$hRzxJRr9EaDb7O8UR0MKE=.#=qPlbkma4EyaAamon3FlrJIQ==(Int32 #=q3Pg_1bowvJy2R4F5Y3e9Yw==, String #=qKT54DGjqSCSJ8L8mCzrcBA==, Object #=q3e9ImqnUASgbiPk9wVPTLQ==, Bitmap #=qeuERM22msxfmdCwSDSf2_A==)
   bij #=qFVnTf5SxxoEB5tLlkoLvh$hRzxJRr9EaDb7O8UR0MKE=.#=qMOwvbmE8ZwtIkEyfJaIAAQ==.#=qgdlQc0wiWtpeM8pP44wYqA==(IList`1 #=qpMaxTYSs201wYXGiU5aAlQ==)
   bij #=qFeTrPQ3tnQM_SwIKR1lwKgbkVkUdCZn7pqLCF6ziBDk=.#=qzp2QEhq4Z32Zg3psb_sM80x4CAKpjEKxS6fZJ6xue$s=(#=qMOwvbmE8ZwtIkEyfJaIAAQ== #=qxG$eOmQ_Y4gPymAYJIEn7A==, Boolean #=qxuIfmIG2_oxFdCWzfKdxVzJjy7_AEy_GKuOwoGPTF_Y=)

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 35003
what were you doing?
I cant be sure from the log but it appears you are expanding a folder in the computer tree and is the error displayed with a custom message or just an "unexpected error" ie. did you get the above from the error log
I would need to give you a debug version to see what is going on, so please confirm you are happy to run a debug version
Last Edit: May 11, 2016, 12:14:02 PM by Steven

peewee678

  • Full Member
  • ***
  • Posts: 143
To be honest I wasn't really focused (there *was* a dialog with probably an "unexpected error") but I will pay more attention next time.
A debug version would be nice. Thanks.



peewee678

  • Full Member
  • ***
  • Posts: 143
Hi Steven,

It just happened again (Note: I was not using the debugging version yet) and I now know what happens:
I'm working in a MS Word document, select some text and cut it to the clipboard. MB pops up with a crash dialog. It says something about one of the VST plugins "DeePanpot.dll" I'm using but note: MB never crashed; it only happens in this specific scenario.

To make things more complicated: I can't replicate it immediately after, but I do remember this is what happened each time since yesterday (I almost never use Word but I had to write a letter yesterday and this day).

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 35003
the error you posted earlier relates the expanding a node in the Computer section of the navigator tree. I cant see how its connected

peewee678

  • Full Member
  • ***
  • Posts: 143
Neither can I. The only thing I can guarantee I was working in Microsoft Word with MB running in the background each and every time the error occurred. I never experience crashes when expanding a node in the computer tree.

I know how to reproduce it now.
NOTE: it only happens with a VST plugin enabled! (doesn't matter which one, reminds me of a previous VST related bug months ago)

- Play a track (optional)
- Open Word or Excel or PowerPoint
- Select text in Word or Excel or PowerPoint
- Cut or Copy the selection (with keyboard or menu; doesn't matter)
- MB Crash!

Again and again. Repeatedly.

Because you're reporting the expanding node thing: could it be related to the bug you weren't willing to fix a little while ago? This one: http://getmusicbee.com/forum/index.php?topic=18160.msg109434#msg109434 (this is just a non-substantiated intuitive idea :-).
Last Edit: May 11, 2016, 05:39:07 PM by peewee678

redwing

  • Guest
Does that crash only MB? Try running other apps along with Word to see if they get affected too by that action.

peewee678

  • Full Member
  • ***
  • Posts: 143
Yeah, only MB.

I always have quite some apps open at the same time (Thunderbird, uTorrent, Total Commander, Firefox, SublimeText, Notezilla, SyncBack Pro, Volumouse, TeamViewer, Logitech software, StrokesPlus, Dropbox, Media Player Classic,  MS Security Ess. etc. etc.)

I know this must sound like a preposterous, ugly, weird bug again but hey, don't shoot the messenger ;-)

I use Word every once in a while and Excel a bit more often but never had any problems.

I'm pretty sure Steven is able to reproduce this if he enables a VST plugin. The bug doesn't bug me that much (because I don't use those MS products that often); I'm just reporting it because I'm pretty sure everyone with a VST plugin enabled and using MS Word or Excel will run into the same problem and because some bugs can be a symptom of a larger underlying problem.

NOTE: Just tried a simple cut in a text selection of PowerPoint and, as expected, same results so it's obviously a conflict between MS Office products (or a framework they make use of, like .NET (?) wild guess here) and the VST support in Musicbee...
Last Edit: May 11, 2016, 04:57:51 PM by peewee678

phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 10290
I'm pretty sure I read recently where Steven said he doesn't have MS Office.  So I just tried using Word 2010 and MB 3.0.5973 and can not reproduce the issue.
Download the latest MusicBee v3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Custom Forum Search
Posting screenshots is here

peewee678

  • Full Member
  • ***
  • Posts: 143
Thanks Phred, but do you have a VST plugin enabled? (BTW: I'm using Office 2007)

phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 10290
Thanks Phred, but do you have a VST plugin enabled? (BTW: I'm using Office 2007)
I did not. But I just enabled one of the built-ins and still can't reproduce your issue.
Download the latest MusicBee v3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Custom Forum Search
Posting screenshots is here

peewee678

  • Full Member
  • ***
  • Posts: 143
I'm not referring to the general DSP plugin's. It only happens when using a VST (not a built-in DSP).
There are no VST plugin's in MB unless you installed one.

And another thing: you have to open Word while MB is running (i.e. it does not crash when Word (Excel or Powerpoint) was already opened and only then you start MB). Only then, when Copying or Cutting, MB crashes.

So as you can see: there's all kinds of conditions for the bug to occur but I can still faithfully replicate it each and every time (then again: I have Office 2007 on Win7 x64 so I don't know what happens with Office 2010 and/or Win8/10).
Last Edit: May 12, 2016, 07:53:41 AM by peewee678

redwing

  • Guest
I have Office 2007 and followed your steps but can't reproduce the issue.

- Play a track with MB with DeePanpot plugin enabled
- Open Word and cut/copy text

No crashes at all.
I suspect it's a conflict between Office and one of your background running programs.