Closed
Bug 500766
Opened 15 years ago
Closed 15 years ago
silent crash when loading gmail
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: u279076, Unassigned)
Details
(Whiteboard: [fennectestday])
STR: 1. Start Fennec 2. Navigate to gmail.com 3. Login RESULT: Fennec silently crashes when gmail's loading progress bar nears the end. EXPECTED: GMail should load or at least crash with a reporter.
Updated•15 years ago
|
Whiteboard: fennectestday
Updated•15 years ago
|
Whiteboard: fennectestday → [fennectestday]
I'm seeing this crop up with other browsing too. For example, leaving fennec idle for a few minutes, clicking a link from digg. Running from terminal, I see this output: pure virtual method called terminate called without active exception Aborted
Updated•15 years ago
|
Severity: normal → critical
https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg try using /fennec instead of /firefox attach windbg when you get the dialog, !analyze -v -f ~* kp attach the log.
oh brother. sorry, for some reason i was reading this along with other bugs which i thought were based on the windows version of fennec. if you're using maemo, um https://developer.mozilla.org/en/Debugging_Mozilla_with_gdb b printf b fprintf b exit b abort c
I can't seem to get fennec to run with gdb. I see no different output running "fennec -g -d gdb" than I do "fennec".
Comment 7•15 years ago
|
||
Anthony - Some info on debugging on Maemo here: https://wiki.mozilla.org/User:MarkFinkle/MaemoDebugging
Comment 8•15 years ago
|
||
I tried loading GMail on my n810 after landing the cache patch in bug 448073. GMail loaded for me and I was able to open and read some email.
Comment 9•15 years ago
|
||
My best guess is that this was fixed by the cache patch, so I'm closing it out. If you see it again, please reopen.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 10•15 years ago
|
||
This still crashes for me on Maemo on my 810 using the 7/19/2009 build.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•15 years ago
|
tracking-fennec: --- → ?
Comment 11•15 years ago
|
||
could this be a memory issue?
Comment 12•15 years ago
|
||
I wonder if turning on virtual memory on the N810 would make the difference. I have seen a similar problem going to a totally different site (http://www.pbs.org/newshour) with both 1.0b2 and 1.0b3. In fact, I would get the exact same messages at the terminal ("pure virtual...") if I ran "fennec" from the command line. Today after installing 1.0b3 I ran into the same problem. Before submitting bug about the problem, I happened to notice the suggestion from Bug 511451 regarding turning on virtual memory on the N810. After doing that, I didn't get the crash any more with http://www.pbs.org/newshour . I was actually able to look at the page and listen to various news stories. It's worth a try.
Reporter | ||
Comment 13•15 years ago
|
||
I suspect many crasher bugs with Fennec relate to memory and can be resolved by turning on virtual memory. However, for whatever reason, I can't seem to enable it on my N810. This is conceivably a serious issue for other users who cannot enable virtual memory.
Comment 14•15 years ago
|
||
I had a similar issue with my N810. At first, I enabled virtual memory with a size of only 24 MB just to be conservative. Enabling virtual memory worked as did Fennec once virtual memory was enabled. I tried changing the size of the virtual memory to 128 MB and got errors saying that it couldn't enable virtual memory, giving me a message like "Unable to create virtual memory". At that point, no matter what size I chose for virtual memory, I couldn't get virtual memory working again. Eventually I came across the following solution: http://talk.maemo.org/showthread.php?t=18043 . It comes down to a latent problem in the formatting of the internal 2GB memory card on the N810. If you back up the data from the internal card (/media/mmc2), reformat the card, and then restore the previous data, there is a good likelihood that you can get virtual memory working (assuming you have the space) through the Control Panel. It worked pretty smoothly for me. BTW, I tried the "File Manager" approach for reformatting since it was substantially easier and it worked just fine. The only odd thing that I remember from the whole process was that I have a few files that could not be backed up properly using "tar", possibly due to the formatting problem. I ended up deleting them so that my "tar" archive would complete error free. Anyway, it might be worth a try to get virtual memory working.
Comment 15•15 years ago
|
||
This works on build: Mozilla/5.0 (X11; U; Linux armv6l; en-US; rv:1.9.2a2pre) Gecko/20090903 Fennec/1.0b4pre ...due to the patch in bug https://bugzilla.mozilla.org/show_bug.cgi?id=503784
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → FIXED
Comment 16•15 years ago
|
||
verified FIXED On build: Mozilla/5.0 (X11; U; Linux armv6l; en-US; rv:1.9.2a2pre) Gecko/20090921 Fennec/1.0b4pre
Status: RESOLVED → VERIFIED
Updated•14 years ago
|
Component: Linux/Maemo → General
OS: Linux → Linux (embedded)
QA Contact: maemo-linux → general
Hardware: Other → ARM
Assignee | ||
Updated•11 years ago
|
tracking-fennec: ? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•