Can you let know whoever looks after the blog that it is crashing with the latest firefox 11.0. Not immediately on getting a page up, but when the loading is finished. If I interupt it's downloading with the stop button it's ok for that page.
Did you file a bug report at Mozilla?
CC: (none) => oliver.bgr
Could not reproduce here with Firefox 11.0 either. Could you: * report your exact system config (OS, version, Firefox version and build - see about:buildconfig) * report the matching crash log (see about:crashes) or track in the log what could have triggered the crash. In the meantime, I'll check what could see strange in the blog behaviour. Thanks.
Keywords: (none) => NEEDINFOStatus: NEW => UNCONFIRMEDCC: (none) => rdalvernyAssignee: mageia-webteam => rdalvernyEver confirmed: 1 => 0Severity: normal => major
Mozilla was auto-reported twice at the time OS can be Puppy Linux or Mageia1, both give the same result. ---------- about:buildconfig Source Built from http://hg.mozilla.org/releases/mozilla-release/rev/b967d9c07377 Build platform target i686-pc-linux-gnu Build tools Compiler Version Compiler flags /tools/gcc-4.5-0moz3/bin/gcc gcc version 4.5.2 (GCC) -pedantic -Wall -W -Wno-unused -Wpointer-arith -Wdeclaration-after-statement -Wcast-align -W -Wno-long-long -fno-strict-aliasing -pthread -ffunction-sections -fdata-sections -pipe -DNDEBUG -DTRIMMED -g -fprofile-use -fprofile-correction -Wcoverage-mismatch -O3 -fomit-frame-pointer /tools/gcc-4.5-0moz3/bin/g++ gcc version 4.5.2 (GCC) -fno-rtti -pedantic -Wall -Wpointer-arith -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wcast-align -Wno-invalid-offsetof -Wno-variadic-macros -Werror=return-type -Wno-long-long -fno-exceptions -fno-strict-aliasing -std=gnu++0x -pthread -ffunction-sections -fdata-sections -pipe -DNDEBUG -DTRIMMED -g -fprofile-use -fprofile-correction -Wcoverage-mismatch -O3 -fomit-frame-pointer Configure arguments --enable-update-channel=release --enable-update-packaging --enable-official-branding --enable-stdcxx-compat ------------------------------ From what I think is the Mageia1 crashlog: X_CreatePixmap: BadAlloc (insufficient resources for operation); 18 requests agoxpcom_runtime_abort(###!!! ABORT: X_CreatePixmap: BadAlloc (insufficient resources for operation); 18 requests ago: file /builds/slave/rel-m-rel-lnx-bld/build/toolkit/xre/nsX11ErrorHandler.cpp, line 190) ------------------------------ What gets me, is that I can see what's there as long as the download 'circle' is spinning or if I manually stop it, if I let it 'complete' it errors out! and yes, it still happens!
Additional questions: - does it crash on both blog home page (http://blog.mageia.org/en/) and an individual article page (say, http://blog.mageia.org/en/2012/04/05/revised-release-schedule-for-mageia-2/)? - what happens if you disable javascript prior to loading the blog page?
Thanks Romain, Yes, any blog page, and as I said it's only if the page completes it's download, If I interupt with the stop button it's OK. I need javascript for a couple of my addons, but it works ok on other blog and related websites, just yours crashes (so far). And I also tried Midori earlier and the problem DID NOT appear then. regards
(In reply to comment #5) > I need javascript for a couple of my addons, Right, but I'm just asking you to deactive Javascript for this very test, to make sure it's caused by a JS piece (likely, but I can't find a track yet and reproduce), or not. :-)
ok, didn't understand, sorry no, that didn't fix it, I even disabled flash in case that was the problem, but that wasn't it either! maybe I need to rebuild my ff config in case something has corupted, give me a day or two, as there is an awfull lot in it, even if I don't add my bookmarks files.
no, same result, sorry
and, just as a last thought, I 'shifted' my config away from where it should be and started ff11 up and manually tried to get the blog, it still crashed! I wonder if a paage or script on it's been barred somewhere in the stream between it's server and my isp? I shall ask them to investigate that possability, so leave it for a day or two..
no, isp can get it ok, damn! also deleted, rebooted and reinstalled ff11 so that's not it blast! wonder it it's a lib version problem, next to work out (me), would have thought ff would check before allowing install.
you may be happy to know after all this, that it's a firefox problem! If I understand it correctly from a ff chat overnight: Although I have glx1.3+ installed for my intel video, i'm not using it, using direct rendering instead as I have problems elsewhere with it and awaiting driver fix. The install process for ff11 requires it to be 1.3+ and active to do everything however it only checks for it's presence, not it's actual use! closing the bug
Status: UNCONFIRMED => RESOLVEDResolution: (none) => FIXED