Is it possible to force your play app to run in the browser, even though it has errors? This is so that I can more easily see the errors in the browser instead of searching through them in the console.
I am refactoring something which has over 300 errors, and thought it might be easier to see them one at a time in the browser.
Thanks!
I'm afraid there's no possible way of achieving what you desire. You can't run an application with compilation errors. It's like driving a car without wheels. The console and your IDE are your friends.
Related
I'm looking for some tool that can allow writing media queries in real time, while doing something like - inspecting in google chrome and adjusting code as needed. One such tool is shown in this video-
https://www.youtube.com/watch?v=kXTP8XqrSwE&t=613s
But it's not maintained anymore and seems broken now. So, fellow developers please share anything similar or better than this tool that might be of some help.
I have developed my website with asp.net and c# with MySql as back end. But even after optimizing css, Javascript and Images still takes time to load my website www.cloudionpro.com.
Please help do I need to change something in my coding or its a mysql server issue?
I loaded your site in Chrome and is reported the HTML of the page itself loaded in 93ms, of which 51ms was spent waiting for the HTML to be generated. 51ms is acceptable, but probably could be improved: it's likely you're making a lot of MySQL database calls that could be optimized (by paralleising them, or executing a query-batch).
Chrome reports the Google Maps API you're using failed to load, caused by scripting errors, which is also causing problems, open your browser's console for details of those. It looks like your site has a dependency on jQuery but your site never loads it.
I was wondering if anybody could direct me to any tools for debugging the cache.manifest file in offline HTML5 access. I recently downloaded a program called Manifesto which allows me to look up the cache manifest on loading a page. Everything seems to working fine however it keeps on saying that the status is "uncached". Obviously, it seems like although it is checking to make sure the cache files are there, it isn't actually caching them upon load. Whats going on and more importantly, how do I figure out how to solve it?
I got it to work. To be honest, it might have been working before but because I was having some different php scripts running in the background I had to be a little careful with pulling it up.
My browser extension is crashing occasionally. The problem is, I cannot find a good, comprehensive list of things that can cause an extension to crash, and thus am having a hard time creating a checklist of things to work with.
My assumption is that anything that causes a standard Chrome tab to crash would cause the extension to crash when run in the Background.html file.
Off the top of my head, I'm assuming the following could cause problems...
Infinite loops or other instances of a script becoming unresponsive
Uncaught exceptions (eg, a JSON.parse with no try/catch)
Database storage errors
Excessive resource usage (??)
That's really all I can think of. I'm having a heck of a time trying to debug my extension and would really appreciate any help creating a checklist...
I'm coming back to this question about 3 months after asking it because a 2nd extension of mine was also crashing. In this case, though, the extension was far simpler -- only about 40 lines of code in the background.js script.
2 operations seemed to be possible culprits: writing to localStorage and using console.log
I have previously observed that it is possible to crash a normal chrome tab by using console.log repeatedly with large objects in a website if you leave the page open for an extended period. Because background.js is always open, it seems like a likely culprit here.
tl;dr
Don't use console.log in production. Ever.
I've searched the Internet like crazy, however "WTP freeze" or "Eclipse freeze" yields so many different results that it's virtually impossible to find the right one. I have the following issue.
In a HTML or CSS editor when I accidentally hover my mouse over an attribute value, Eclipse hangs for 3-4 seconds with CPU at 100% load before producing a tooltip message with some info on the tag and its attribute. I don't need those tips. Hell, I don't even need syntax coloring if that would prevent me from this hang.
I tried disabling all the autocomplete features, everything that seemed related, however that didn't change a bit. I looked for a setting to disable WTP completely without uninstalling it, however again - no luck.
I use Eclipse Helios. I have all the latest plugins. I'll supply any additional info, if that is needed.
Has anybody had a similar issue and was able to resolve it? This is really driving me crazy.
BOUNTY
The bounty will go to anyone who finds a way or a workaround that will make pop-up windows reasonably fast. I've had this issue in Eclipse in numerous places - like PyDev for example:
Eclipse PyDev completion hangs (yet again)
I have a strong programistic feeling that this is a general issue with pop ups and not so much with WTP/PyDev. Here are measures that I've already taken:
Installed the latest Eclipse from scratch
Installed the two problematic plugins on this clean installation (WTP/PyDev)
Made sure that Eclipse has more than enough memory
Made sure the appropriate JVM is chosen
My setup is Ubuntu Natty, Oracle Java 1.6 - latest version in the repos
Further findings
Ok, I've just found out that 99% of the time of the freeze is spent inside a call to org.eclipse.swt.internal.gtk.OS._gtk_widget_realize which doesn't seem right. Any clues?
I'd encourage everyone who has experienced this issue to vote for this bug on the Eclipse bug tracker.
You could try switching off all the Validators: Window > Preferences > Validation > Suspend all validators.
Another option is Window > Preferences > Java > Editor > Hovers, turn off 'Combined Hover'.
Wow, finally nailed it, thanks to one of the suggestions.
Hover messages can be disabled under Window > Preferences > General > Editors > Structured Text Editors > Hovers tab > Combined Hover.
Eclipse can be a labyrinth sometimes.
I had a similar issue where Eclipse would hang on tooltips for several seconds, and oftentimes crash. It got to the point where it would just plain crash even if I didn't do anyhting. Uninstalling it and reinstalling it got rid of the problem, though, so I suggest giving that a try if you haven't already.
How is your memory profile? Do you have more than enough?
We have run into many problems with Eclipse and wierd issues as we approached our memory limits. The current prevailing thought is that the swapping causes problems due to timing issues.
Eclipse sometimes downloads the the javadoc as requested, the hang your seeing may be the lag time it takes for that particular part of the javadoc to download.
The selected answer didn't work for me in Eclipse (Kepler) with PyDev.
For me the following worked best:
Show Docstrings should be disabled in preferences under Pydev/Editor/Hover.
This looks to be a gtk specific issue. In addition to the bug you mentioned there are other bugs opened as well e.g. https://bugs.eclipse.org/bugs/show_bug.cgi?id=345093.