Skip to content
This repository has been archived by the owner on Jun 14, 2018. It is now read-only.

Hard crash trying to open files in rapid succession #39

Closed
peterflynn opened this issue Jan 31, 2012 · 8 comments
Closed

Hard crash trying to open files in rapid succession #39

peterflynn opened this issue Jan 31, 2012 · 8 comments

Comments

@peterflynn
Copy link
Member

Steps:

  1. Press Ctrl+O to bring up the Open File dialog
  2. Double-click a file in the list to open it
  3. Repeat 1-2 a few times

Result:
Brackets terminates suddenly one of the times you hit Ctrl+O. I seem to get it in < 5 tries every time.

I tried to repro this on Mac but no luck*, so I'm assuming it's Windows-only.

(* for a slightly twisted definition of "luck")

@ghost ghost assigned gruehle Jan 31, 2012
@peterflynn
Copy link
Member Author

Oops, I actually just repro'ed this by going through the HTML File > Open command too. So it seems like any rapid-fire invocation of the file-browse dialog and its associated JS command will cause a crash after a few attempts.

Changing title...

@peterflynn
Copy link
Member Author

And to clarify: this does not happen if you simply open documents rapidly by clicking/double-clicking many in a row via the project tree. You have to go through the native Open dialog to get a crash.

@gruehle
Copy link
Member

gruehle commented Feb 1, 2012

This bug appears to be Win XP only (or perhaps Peter's machine only). Several of us cannot repro on Win 7.

@peterflynn
Copy link
Member Author

Here's the exception info I can get without symbols:
Unhandled exception at 0x7c9012b0 in Brackets.exe: 0xC0000005: Access violation reading location 0x05b01000.

The read location address varies each time, but the code offset is always the same.

@peterflynn
Copy link
Member Author

I have a home machine that still runs XP also... I'll try there tonight for a second data point.

@peterflynn
Copy link
Member Author

No luck reproing on my home PC with XP...

@gruehle
Copy link
Member

gruehle commented Feb 3, 2012

Fixed in pull request #45. Assigning to Peter to close.

@peterflynn
Copy link
Member Author

Oops, already verified this fix earlier

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants