search

zhangqd / chromiumembedded

Automatically exported from code.google.com/p/chromiumembedded
0 stars 1 forks source link

Windows: 64-bit build using VS2013 on Windows 8.1 always shows console window #1246

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Whenever application starts and the browser is being loaded
2. Each time there is an error that is supposed to go into debug.log, it is 
written into that window.
3.

What is the expected output? What do you see instead?
I do not want to see that window. (It looks like a command prompt window)

What version of the product are you using? On what operating system?
3.1846.1637, on windows 8.1

Please provide any additional information below.
Also, whenever I try to close, it reappears.  Looks like it's running as a 
separate process.
Is there a way to get rid of that window?
Thanks.

Original issue reported on code.google.com by igor.y...@gmail.com on 4 Apr 2014 at 12:45

GoogleCodeExporter commented 9 years ago 
Does the problem occur with the cefclient sample application? What Visual 
Studio version are you using? Does it occur with both Debug and Release builds?

Original comment by magreenb...@gmail.com on 4 Apr 2014 at 2:26

GoogleCodeExporter commented 9 years ago 
It happens with the main application.  I am using VS 2013.  Yes, it happens 
with both builds.
I have been searching through all possible command line switches.  
I tried settings.log_severity = LOGSEVERITY_DISABLE;  But it only prevented 
messages from going to debug.log.

Original comment by igor.y...@gmail.com on 4 Apr 2014 at 3:27

GoogleCodeExporter commented 9 years ago 
I just checked the "simple" version.  It has the same problem.

Original comment by igor.y...@gmail.com on 4 Apr 2014 at 4:07

GoogleCodeExporter commented 9 years ago 
Using cef_binary_3.1846.1637_windows32 on Windows 8.1 with VS2013 update 1 I 
see the console window with the Debug build but not the Release build.

Are you sure you're seeing it with the Release build?

Original comment by magreenb...@gmail.com on 4 Apr 2014 at 7:11

GoogleCodeExporter commented 9 years ago 
Yes.  But I am using Windows 64.  Btw, that problem does not occur when the 
application is running on Windows 7.

Original comment by igor.y...@gmail.com on 4 Apr 2014 at 7:12

GoogleCodeExporter commented 9 years ago

Original comment by magreenb...@gmail.com on 4 Apr 2014 at 7:31

GoogleCodeExporter commented 9 years ago 
?

Original comment by igor.y...@gmail.com on 5 Apr 2014 at 4:10

GoogleCodeExporter commented 9 years ago 
So, it's a console window.  Now I am trying to use console object but it's not 
recognized.  Is there a header I need to add?

Original comment by igor.y...@gmail.com on 5 Apr 2014 at 12:14

GoogleCodeExporter commented 9 years ago 
This appears to no longer be a problem with newer branches (2171+) and Visual 
Studio 2013 Update 4 using the cmake build.

Original comment by magreenb...@gmail.com on 11 Feb 2015 at 7:54