Sounds buggy. File a bug at new.crbug.com so they will investigate. Give as much information as possible. Thank you!
☆PhistucK On Tue, Jan 12, 2010 at 12:19, Manticore <mantic...@gmail.com> wrote: > I'm using existing plug-ins on the users PC, like Windows Media Player > plug-in, but I'm not including my own custom ones, so it shouldn't be > a problem. I'm not using the file://*/ permission either. > > I remember this happening when I tried to change the description of > the extension, and I happen to click the Update File button instead of > Publish. After that moment it has said it needs to be reviewed before > publishing. > > Could this be a bug? > > Manticore > > On Jan 12, 6:21 am, PhistucK <phist...@gmail.com> wrote: > > Do you use "file://*/" in the "permissions" section? > > Or do you have an NPAPI plugin in your extension? > > > > These are the reasons for it to be pending approval. > > > > ☆PhistucK > > > > > > > > On Tue, Jan 12, 2010 at 01:43, Manticore <mantic...@gmail.com> wrote: > > > Sorry for the excessive posting. > > > > > I have now updated my extension, and haven't noticed any crashes > > > since. My only problem now is that the extension gallery wants to > > > review it before publishing. Yet I don't use any features requiring > > > review. Would someone please take a look at it? I'd very much > > > appreciate it! > > > > > Thanks > > > Manticore > > > > > On Jan 12, 12:28 am, Manticore <mantic...@gmail.com> wrote: > > > > I've submitted first bug report now (maybe the only one!): > > >http://crbug.com/32017 > > > > > > Manticore > > > > > > On Jan 11, 9:54 pm, Manticore <mantic...@gmail.com> wrote: > > > > > > > George, Thanks for your reply! > > > > > > > >>Though the previous versions would just ingore such issues, this > one > > > > > >> - and thats a good thing since we are forced to make our > extensions > > > > > >> stable & valid - will not, resulting in crashes. > > > > > > > I'm pretty strict on defining variable etc, but I'm sure I could > have > > > > > missed it somewhere. Though, the extensions should not crash if > they > > > > > have undefined variables etc - there should be exceptions shown. > > > > > > > Thanks for your tips, I'll try it. > > > > > > > @Adam Barth > > > > > > > >>Would you be willing to file a bug with some test cases? > Extensions > > > > > >>shouldn't be able to crash a tab or the browser. (Also, it would > be > > > > > >>helpful if you let me know the bug number.) > > > > > > > Sure, I'll try that. Not sure I will be able to make it though, as > the > > > > > problems usually occurs when it's all connected. > > > > > > > Thanks! > > > > > > > On Jan 10, 10:24 pm, Adam Barth <aba...@chromium.org> wrote: > > > > > > > > Would you be willing to file a bug with some test cases? > Extensions > > > > > > shouldn't be able to crash a tab or the browser. (Also, it would > be > > > > > > helpful if you let me know the bug number.) > > > > > > > > Thanks, > > > > > > Adam > > > > > > > > On Sun, Jan 10, 2010 at 12:36 PM, George Papadakis > > > > > > > > <phaiston...@gmail.com> wrote: > > > > > > > 288.1 is a way less forgiving version compared to the previous > > > ones. > > > > > > > > > Make sure all your variables are defined, and that yout DOM > > > references > > > > > > > are valid. Though the previous versions would just ingore such > > > issues, > > > > > > > this one - and thats a good thing since we are forced to make > our > > > > > > > extensions stable & valid - will not, resulting in crashes. > > > > > > > > > I spent more than an hour debugging extensions after this > release > > > came > > > > > > > out, and I was amazed so many things were not done right, still > > > they > > > > > > > just worked. > > > > > > > > > What's frustrating is that there is no kind of pre-logging or > any > > > > > > > other way to debug those crashes. > > > > > > > > > Still, you can alwaty apply the traditional "alert and return" > > > > > > > methodology. > > > > > > > > > Good luck. > > > > > > > > > On Jan 10, 8:03 pm, Manticore <mantic...@gmail.com> wrote: > > > > > > >> Hi, > > > > > > > > >> I've been debugging my extension now for hours and haven't > been > > > able > > > > > > >> to pinpoint the problem to a certain method or even file, thus > > > making > > > > > > >> it quite hard to describe the problem here. I'll try to > describe > > > as > > > > > > >> detailed as I can. > > > > > > > > >> The crashings started after the dev updated from version 266 > to > > > 288.1. > > > > > > >> The extension was working fully on the 266 version and hasn't > been > > > > > > >> changed since. > > > > > > > > >> I have tried disabling methods/features one after one to see > if it > > > > > > >> helps, and these are things that have helped (but didn't solve > > > > > > >> totally): > > > > > > >> - Removed a method that calls the background page from popup > > > before > > > > > > >> 'load' has fired. > > > > > > >> - Removed 'unload' handler that calls a method in background > page. > > > > > > >> - Removed timers from background page. > > > > > > >> - Removing sendRequest calls from bg. > > > > > > > > >> It's really hard to know why the extension is crashing as it > just > > > > > > >> disappears without any exceptions shown. Is there any log file > > > saved > > > > > > >> somewhere where I can read the exceptions? > > > > > > > > >> Are there any major (or minor, for that matter) changes to the > > > > > > >> extension system between 266 to 288.1? > > > > > > > > >> Another weird behavior is that sometimes when my extension > > > crashes, > > > > > > >> another (to me random) extension crashes too. > > > > > > > > >> The extension I'm talking about is: > > >https://chrome.google.com/extensions/detail/hgjdhckebbdoobhniheihpdog. > .. > > > > > > > > >> I realize I'm very diffuse here, but I will appreciate any > help I > > > can > > > > > > >> get. > > > > > > > > > -- > > > > > > > You received this message because you are subscribed to the > Google > > > Groups "Chromium-extensions" group. > > > > > > > To post to this group, send email to > > > chromium-extensi...@googlegroups.com. > > > > > > > To unsubscribe from this group, send email to > > > chromium-extensions+unsubscr...@googlegroups.com<chromium-extensions%2bunsubscr...@googlegroups.com><chromium-extensions%2Bunsu > bscr...@googlegroups.com> > > > . > > > > > > > For more options, visit this group athttp:// > > > groups.google.com/group/chromium-extensions?hl=en. > > > > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "Chromium-extensions" group. > > > To post to this group, send email to > chromium-extensi...@googlegroups.com. > > > To unsubscribe from this group, send email to > > > chromium-extensions+unsubscr...@googlegroups.com<chromium-extensions%2bunsubscr...@googlegroups.com><chromium-extensions%2Bunsu > bscr...@googlegroups.com> > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/chromium-extensions?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Chromium-extensions" group. > To post to this group, send email to chromium-extensi...@googlegroups.com. > To unsubscribe from this group, send email to > chromium-extensions+unsubscr...@googlegroups.com<chromium-extensions%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/chromium-extensions?hl=en. > > > >--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To post to this group, send email to chromium-extensi...@googlegroups.com.
To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
