firefox extension crashes for none reason - javascript

I have one extension for firefox done, no erros on the code, everything is working, but for some reason sometimes stop working and make firefox crash. I made a lot of testes and different cases.
My question is, how can I debug this extension?
There's some way quicker to install the extension then everytime I make some change I need to compress to zip, uninstall and reinstall again the extension.
I'm using Firefox 25.0 on Ubuntu 13.10

You can Open about:crashes page in Firefox there will be a lot of info about your Firefox crashes(if it really crashes). If this is just JavaScript errors, try using Firebug or JavaScript console to get more info

Related

PgAdmin for Windows in the latest version (4.28) doesn't start anymore, hangs in the loading screen and shows JavaScript errors in the browser console

PgAdmin in the latest version (4.28) doesn't start anymore, hangs in the loading screen and shows JavaScript errors in the browser console. What can I do?
The solution is simple although I don't really know why it occurs from that version on:
Open the registry editor (Search for regedit.exe)
Run it as administrator
Navigate to Computer\HKEY_CLASSES_ROOT\.js
Adjust Content Type from text/plain to text/javascript
Restart pgAdmin and it should work again.
Maybe, you will have to clean your browser cache or restart your computer as well (Thanks to the Kassym and Bruce).
As already I said, I have no idea why or how this happens, maybe someone from the team can add this as a comment here and I will update my answer.

Debug JS Remotely vs Debug in Chrome

Some time I am getting
Debug JS in remotely and other time
Debug in chrome.
Now I really don't know when and how this option changes and the process to handle the scenario for Debug JS Remotely.
In my case when i click on Debug JS Remotely nothing is happening at my pc. I think it should open chrome in debug mode.
I'm not sure but I think those two text means the same thing, when packager is running try access this url on your browser.
http://localhost:8081/debugger-ui

createjs load local files loadqueue

Im have been working on a project with the createjs library and I have used Brackets with Live preview where everything works perfectly, but if I just open the file in a browser I get the following error message in chrome.
XMLHttpRequest cannot load file:///C:/Users/Maskinen/Docuemnts/fail.fail. Cross origin requests are only supported for HTTP.
I have read that if I set loadqueue(false) I wouldnt get problems with loading local files. I therefore thought that when it was working in live preview in brackets everything was fine. Is it possible to run chrome or firefox as Brackets in live preview or similar? The project is part of an assignment and it isnt possible to use a webserver :(
This it what is found by searching around for a bit:
If you launch chrome.exe like this it should work
chrome.exe --args --disable-web-security
When you're done restart chrome without the args and it works like normal again.
Source:
http://robandlauren.com/2013/09/25/cross-origin-ajax-requests-localhost-chrome/
I prefer to be more specific to it and use allow-file-access-from-files flag.
To do that execute chrome with this option:
Windows
cmd
chrome --allow-file-access-from-files
Mac
bash
open /Applications/Google\ Chrome.app --args --allow-file-access-from-files
Even thought this is disabling security protections so be careful with it, and enable it back to browse securely 😀

How do I debug a mobile Safari crash that works on iPhone 5, but not 4S

I'm not even sure where to begin. Page loads fine on my 5, but not my 4S. Instead it crashes the browser to the home screen.
Without sharing the specific URL, can you point me in the right direction to debug this?
There are no discernible errors in Firebug or other debugging tools on my computer.
You should be seeing a crash report in Xcode organizer and an exception on the command line. Since this is an Apple app you should report this as a Radar.
Does your 5 have a newer version of safari?
Use the iOS simulator if you have it, and then try running with different versions of safari, you can get a log output from it, especially if you are using dashcode, otherwise I think it is in the system logger. That is, if you have a Mac.

Javascript debugger issue in VS2008

I'm having a really annoying problem with debugging javascript with VS2008.
If I simply press F5 (or choose 'start Debugging' from the Debug menu), the iexplore process is attached, but no breakpoints break in the scripts. The Script Documents tree doesn't even appear in the solution explorer.
I already know:
I can set a breakpoint in Javascript just fine. It does NOT show the "This point will not be hit" message.
Calling the debugger through using the 'debugger' keyword works fine, but attaching to the iexplore process doesn't since it gives a "process already attached to a debugger" message.
Using the manual 'Attach to process...' works just fine. The Script Documents appears as well.
The project has recently been converted to a Web Application from a WebSite.
I already tried:
Clearing the IE cache.
Shutting down VS2008, Stopping the IIS and deleting the temporary asp.NET files restarting both IIS and VS2008 afterwards.
Setting IE7 as the default browser both for windows and for VS2008.
Resetting my user settings for VS2008.
Checking that IE script debugging is enabled.
Nothing has worked so far. While Attaching to process isn't too taxing, it is very annoying when I'm used to just hitting F5.
If anyone can think of a solution, please please please (I'm begging here!) let me know!
Is silverlight debugging enabled on the website project properties? This will disable Javascript debugging.

Categories

Resources