Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Brackets Crash #143

Open
DigitalFeonix opened this issue Jul 12, 2017 · 3 comments
Open

Brackets Crash #143

DigitalFeonix opened this issue Jul 12, 2017 · 3 comments

Comments

@DigitalFeonix
Copy link

When I use the Windows command prompt to run a PHP file and pipe it to a log file within the project file scope, it will crash Brackets (the window goes gray and "Brackets has stopped working" dialog appears).

Confirmed with testing that it is the Todo extension alone - no other user extensions loaded - that is doing this. The log file doesn't have to be open either.

Steps to Reproduce

  1. Use a script that outputs something and pipe to a file
<?php

echo "We're going to break Brackets now\n";

C:\dev\CLI scripts>php -f break-brackets.php > break.log

  1. Watch Brackets crash

Versions

Todo 0.9.4
Brackets 1.10 32-bit on Windows 7

@DigitalFeonix
Copy link
Author

I updated Todo and re-ran my tests with the same results.

I can give some more info though. When piping to the log file, if it does not exist yet or you are appending then it does not crash. Only when outputing to a file that already exists then it will crash.

will not crash Brackets if file does not exist
C:\dev\CLI scripts>php -f break-brackets.php > break.log

will crash Brackets if file already exists
C:\dev\CLI scripts>php -f break-brackets.php > break.log

will not crash Brackets
C:\dev\CLI scripts>php -f break-brackets.php >> break.log

Versions

Todo 0.9.5
Brackets 1.10 32-bit on Windows 7

@mikaeljorhult
Copy link
Owner

Yes, I have noticed the same thing but haven't found a fix for it yet. Thank you for confirming the results!

@brigevans
Copy link

Also tried to exclude .log file, the file name itself, and also the logs folder, and none of them corrected the issue with the crashing on log files.
image

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

No branches or pull requests

3 participants