Coincidentally I stumbled over this message again. Sorry for the many months without reply!
Newer bug fix releases of Firebug 2 have addressed these issues. So, the current version 2.0.13 should work better in this regard. Meanwhile the Firebug team is working on Firebug 3, which will integrate into the built-in DevTools of Firefox. As I am not part of the team anymore, I don't know when this version will be officially released. Though you can already try it out: https://getfirebug.com/releases/firebug/3.0/ Best regards, Sebastian On Thursday, April 2, 2015 at 2:02:26 PM UTC+2, James Gallagher wrote: > > Hi Sebastian, > > > Thank you for replying. I did not know 1.12.x was not compatible anymore, > that is good to know, thanks :) On the Firebug site beside the download > link it says 'Compatible with: Firefox 23+'. > > The strangest thing; when I went to FF today - opened (Ctrl+Shift+J) > first - interested in what would appear... but Firebug opened... Hadn't > opened for last two days... maybe with the shut down last night, cleared > something out - I don't know why it has started working, but it's great > news :) > > When it started to work though - it got this in the script tag - 'This > Version of Firefox removed the old JavaScript debugging API. Please install > Firebug 2.0, which adopts the new API.' > > The reason for us still using 1.12.x; is we are having trouble with 2.x > > We work on a large enterprise app that is very frontend orientated with a > large JS codebase. With Firebug 2.0.8 running; when loading our pages > (in obfuscated & minified mode), we are getting multiple unresponsive > script alerts on page load, one being: > chrome://firebug/content/debugger/script/sourceTool.js:339 > > Clicking continue gets the page to load but when searching script tab, > Firebug seem to hang, putting Firefox into 'Not Responding`, after a while > these unresponsive script alerts appear repeatedly: > chrome://firebug/content/chrome/panel.js:529' > chrome://firebug/content/bti/inProcess/compilationunit.js:77 > chrome://firebug/content/lib/url.js:111 > chrome://firebug/content/lib/array.js:67 > > Firebug 2.x seems to be having trouble traversing the large JS codebase... > > In debug mode; where JS is not obfuscated & minified - the unresponsive > script alerts do not appear, but it appears Firebug is not able to search > the multiple files loaded with the non obfuscated & minified code. > Searching Script tab puts Firefox into 'Not Responsive', when Firefox comes > out of 'Not Responsive', nothing happens... > > Have you seen this before with Firebug 2.x against large JS codebases? Is > this something the Firebug team are actively working on? > > > Thanks :) > -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/420e5187-2cc9-4b60-98b7-7e0753b93e9e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
