Opened 9 years ago
Closed 8 years ago
#12349 closed bug (fixed)
WebPositive crash on secure website
| Reported by: | vidrep | Owned by: | pulkomandy |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Applications/WebPositive | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | #12351 | |
| Platform: | All |
Description (last modified by )
hrev49606 x86_gcc2 Go to: https://easyweb.td.com/ Webpositive crashes Debug report attached
Attachments (2)
Change History (14)
by , 9 years ago
| Attachment: | WebPositive-759-debug-30-08-2015-18-22-14.report added |
|---|
comment:1 by , 9 years ago
comment:2 by , 9 years ago
| Description: | modified (diff) |
|---|---|
| Summary: | Webpositice crash on secure website → WebPositive crash on secure website |
comment:3 by , 9 years ago
I tried the website with Webpositive in hrev49606 x86_64. It did not crash immediately but after I clicked on "contack" link from home page then after it loaded, clicked the back button, it crashed after a few seconds. In hrev49606 x86 gcc2, it crashed at the home page and froze up the desktop, so I had to do a reset.
comment:4 by , 8 years ago
Navigating the TD website no longer triggers a crash. The ticket can be closed.
comment:5 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:6 by , 8 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
by , 8 years ago
| Attachment: | WebPositive-4326-debug-11-11-2015-16-08-46.report added |
|---|
comment:9 by , 8 years ago
| Blocking: | 12351 added |
|---|
(In #12351) Closing as duplicate, it's probably the same issue causing a memory corruption. Depending on what it corrupts, you get different crashes.
comment:10 by , 8 years ago
I'm still seeing this using hrev49939. Usually if I navigate to the TD homepage first, then click the link to easyweb, it loads without crashing, and I can navigate without problems.
comment:11 by , 8 years ago
I have been using Web+ for on-line banking almost daily and have not seen the problem for some time now. Is it safe to assume that the issue was fixed sometime during the past 3 months?
comment:12 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Can somebody please fix the typo in the description?