Should it work without specifying another profile? I tried having starting Chrome with --disable-hang-monitor only and I am running from FB. It is still prompting me ....
On Tue, Apr 7, 2015 at 8:28 AM, Frédéric THOMAS <[email protected]> wrote: > That allows you to work with another profile / window without interfere > with your existing profile, the one you are potentionally using every day, > useful for example if you personally use chrome with a connection to your > google profile and want a new fresh profile for testing debugging your app, > want to use the NPAPI plugin only when debugging instead of the every day > PPAPI > > You could use another name than Dev indeed, chrome will create a folder in > your user directory to store the settings relative to this profile. > > Google is your friend for more details on Chrome :-) > > HTH, > Frédéric THOMAS > > > Date: Tue, 7 Apr 2015 08:09:32 -0500 > > Subject: Re: Re : Re: Chrome for debugging > > From: [email protected] > > To: [email protected] > > > > Thanks for the info. Can you please explain what would > profile-directory="Dev" > > do? > > > > > > On Tue, Apr 7, 2015 at 4:29 AM, Frédéric THOMAS <[email protected] > > > > wrote: > > > > > Hi Mark, > > > > > > I was with my phone only before and my tweet was showing a image > captured > > > on my desktop setting what you want from IntelliJ, not easy to copy / > > > paste, especially here. > > > > > > Anyway, generally, for debugging you will want to do it on another > Chrome > > > profile/ window and avoid the script execution timeout checking, I > don't > > > know what IDE you are using for development so, I give you the command > line > > > on Windows: > > > > > > "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" > > > --profile-directory="Dev" --disable-hang-monitor > > > > > > Might be something like this on MAC: > > > > > > open -a "Google Chrome" --args --profile-directory="Dev" > > > --disable-hang-monitor > > > > > > And for Linux: > > > > > > google-chrome --profile-directory="Dev" --disable-hang-monitor > > > > > > HTH, > > > Frédéric THOMAS > > > > > > > Date: Mon, 6 Apr 2015 06:15:38 -0500 > > > > Subject: Re: Re : Re: Chrome for debugging > > > > From: [email protected] > > > > To: [email protected] > > > > > > > > I am not on Twitter. > > > > > > > > On Mon, Apr 6, 2015 at 6:06 AM, Frédéric THOMAS < > [email protected] > > > > > > > > wrote: > > > > > > > > > Try this guys > > > > > https://twitter.com/webDoubleFx/status/584413022350876672?s=09 > > > > > > > > > > HTH, > > > > > Fred. > > > > > > > > > > --- Message initial --- > > > > > > > > > > De : "Mark Line" <[email protected]> > > > > > Envoyé : 5 avril 2015 17:32 > > > > > A : [email protected] > > > > > Objet : Re: Chrome for debugging > > > > > > > > > > Don't think you can turn it off in chrome. In Firefox you can turn > the > > > time > > > > > out off. > > > > > > > > > > I tend to use FF for dev (debug player) and keep chrome with the > pepper > > > > > player for normal use > > > > > On 5 Apr 2015 11:46 am, "mark goldin" <[email protected]> > wrote: > > > > > > > > > > > Exactly what I did. Everything is working fine except when I am > in > > > > > > debugging mode sitting on a break point I am getting a message > from > > > > > Chrome > > > > > > that plug-in is unresponsive and if I want to continue waiting. > Is > > > there > > > > > > something can be done about it? > > > > > > > > > > > > Thanks > > > > > > > > > > > > On Sat, Apr 4, 2015 at 1:53 PM, Evyatar Ben Halevi-Arbib < > > > > > > [email protected]> wrote: > > > > > > > > > > > > > Download the Firefox NPAPI debugger version and use that > instead > > > of the > > > > > > > PPAPI versions. > > > > > > > > > > > > > > Good luck, > > > > > > > Evyatar > > > > > > > בתאריך 3 באפר 2015 19:29, "mark goldin" < > [email protected]> > > > כתב: > > > > > > > > > > > > > > > I am trying to follow Adobe instructions how configure > Chrome for > > > > > Flash > > > > > > > > debugging but it is still not working for me. I have > downloaded > > > the > > > > > > > > debugging version ver. 17 for Oepra and Chromium > applications). > > > Then > > > > > > > > disabled the stock one and enabled the debugging version. > Still > > > no > > > > > > luck. > > > > > > > > Any idea? > > > > > > > > > > > > > > > > Thanks > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
