Is anyone else experiencing the same issue when going to wunderground.com for weather information? I upgraded to 10.2 from slackware 10.0, and I get this every time I go to a city or zipcode for local weather.



I tried the 2.4 and 2.6 kernel, changing my video driver from 'mga' to 'vesa', running it as root, creating a completely new user with no previous profile... all give the same error. Disabling images in the browser prefs will allow you to completely load the page, but that's not very useful. Konqueror doesn't have this problem.
Mozilla 1.7.11 and Firefox 1.06 and 1.5x while running in Slackware 10.2 seem to crash the same way. The page nears completion, and then your window disappears.
I don't have any other frequently visited sites that crash the browser this way.

The browser crash does not appear to affect system stability.

It's working fine for me.
But since it's affecting both mozilla browsers (Mozilla and Firefox), I'm inclined to think you need to install java (again. Get the latest at java.com)

That is worth a try...
root@amd:/usr/lib# java -version
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing)

Starting Mozilla, aboutlugins shows that the current java plugin is now the 1.5.0_06-b05 version. Wunderground.com for San Diego still crashes the same way.
The java version that comes with 10.2 is 1.5.0_04-b05, so I wasn't too far behind.



I saw on this forum, as well as other forums for linux, that a java version might cause problems with browsers and a few other applications.

Telling Mozilla to 'do not load any images' will let me finish the page and continue browsing, but that's not very helpful for viewing weather maps.

Here is an interesting bit of information...
I started vncserver locally for root, then launched vncviewer as my user, started firefox in the vnc session, loaded wunderground, and it works just fine inside the session.

Maybe something with X that I'm missing or doing wrong. On version 10.0, this was never a problem. I'm stumped. I have a Matrox 400 single head AGP card.

It works normally with my mozilla browsers.
Java output:My AGP card is NVIDIA GeForce FX 5700, but graphics card can't cause problems if it was working in 10.0 and also works in other browsers.
Did you try reinstalling mozilla and firefox? As well, could you tell us how did you make an upgrade? If using some package manager, maybe not all required files were downloaded from slackware website because you hadn't had them installed before doing an upgrade.

The 10.2 install was on a clean disk. The firefox that came with 10.2 had the problem, as did the mozilla (I installed everything). Knowing that Firefox and Thunderbird were outdated, I got the self installing binary from mozilla.com and removed the slackware packages before installing the new ones. The self-installer just unpacks itself into a directory, so I moved that into /usr/local/firefox and /usr/local/thunderbird, then created desktop links.
The mozilla browser is still the version from the 10.2 media.

I also tried using FWVM for the windowmanager, and it dies with the same error.

Since the browsers work inside vncserver, and they seem to work for everyone else, maybe I have a problem with my X server. My Xorg.0.log only has one error related to the Speedo font. I'll try and find that one next.

I think I've ruled out the Matrox card as the problem, since I'm getting more features from it now than I did in previous versions. I still might use this as an excuse to get an OpenGL card. Since the error message comes from X, and everything except VNCserver is talking to the currently running X server, that's the only common reference I can find. Some image on wunderground.com is telling the mozilla browser to do something that my X doesn't like, and I get BadAlloc messages.

I've got X.org 6.8.2
What is your version?
-Jon

X11 6.8.2 from Dropline. Didn't upgrade to X.org 6.9 because glxgears performance drops down about 3 times after upgrade. Maybe upgrading to the latest Slackware X.org (6.9) will help you.

The self extracting .bin maybe the culprit. Get the firefox package from slackware.com/current, and use installpkg on it. The bins, I have found, don't always do the job in Slackware

I have exactly the same problem. I should mention that i'm using 10.2 and i installed the latest slackware tarball of 1.5.0.1 (from 1.5, i didn't have problems with 1.0.8, at the time, but if i switch back to it i do now) It happens to me in wunderground AND in gmail after the login. This happens like clockwork, 100% of the time. Also, there is nothing following the crash, no feedback agent! nothing! just gone! The only thing that i could think of is that both of these pages are self reloading. The mechanism i don't exactly understand, but i've turned off both java and javascript, but to no avail, it still crashed in exactly the same way. I've been thinking about installing it the old fashioned way, but i'm not confident that this will solve the problem. Any thoughts? If anybody can throw me a bone here i'd be most grateful.

I have personally found the latest firefox to be very unreliable. It crashes quite often, but more often just refuses a connection to google or whatever. So I'm using 1.07 for now.

My 1.5.0.1 is fine, stable, no issues. I works fine on that website.

I just verified that the same thing occurs with the Mozilla Suite which was part of the distro with a clean profile and no extensions. One thing i didn't mention was that i am using the 2.6 kernel. I also have a laptop that has virtually the same Slackware install save for the kernel which is 2.4. It has no problems. All that aside, if i boot the notebook from the 2.6, firefox and mozilla both still work. It seems like this is difficult for other people to reproduce, unfortunately, i have no problem reproducing it. Again and again and again. Even if nobody has ever seen this happen before, could anyone please recommend a troubleshooting proceedure that might give at least some information? I'm not a total newbie so i can follow directions. Thanks. . .

I tried reinstalling this using the 10.2 media. Same results. I tried fetching Mozilla from the current directory on slackware.com, and discovered a few other dependencies (missing /usr/lib/*.so files) and gave up right away.

Then I reinstalled the firefox package from the 10.2 media, and same results.

I did upgrade (the card was free) to an AGP Diamond V770 / Nvidia TNT2 card, and got the Nvidia drivers loaded. The screens paint much faster, but Firefox crashes with the same BadAlloc error.

I'm thinking it's an X thing, but don't know how to debug it.

Telling Firefox/Mozilla to "do not load images" will allow the page to load just fine.

If you launch Firefox and Mozilla from a terminal window, you should see the crash message when you load the problematic pages. Is it the same, and does it say something about BadAlloc? The gmail crash is a new one. I crash on wunderground, but have absolutely no problems with gmail.
I saw crashes using 2.4, 2.6 (both recompiled for high memory and a few other features), stock 2.4 and 2.6 from the install media. I downloaded 2.4.32 from kernel.org, and that's what I'm running now.

I have another system to upgrade to 10.2 when I have time. It is a P4-HT Dell with a dual head nvidia card. When I get that one upgraded from 10.1, I'll let you know if I get the same problem.

Something changed. Here are the things I know of that changed on my system. In an effort to get Inkscape 0.44 compiled and installed on Slackware 10.2, I found myself installing things like Pango, Cairo, GTK+, ATK, Glib, lcms, gtkmm, fontconfig... and maybe a few others. At one point during the process, apps that use some part of what I was changing (Skype is one I found) no longer rendered the text in the menu bar. After completing the necessary packages to fix that problem, I now notice that the fonts in Firefox look slightly different, and Wunderground.com does not crash either the Firefox or Mozilla browser.

So either Wunderground took out the HTML that crashed my browser, or the changes I made fixed the problem.

FYI