Jump to content


Fix the Orange Circle of Death at battle start -- crash

1.7 crash bug orange circle of death

  • Please log in to reply
7 replies to this topic

acrisis #1 Posted 28 February 2015 - 05:48 PM

    First Sergeant

  • Players
  • 20500 battles
  • 11,107
  • [III]
  • Member since:
    12-27-2014
 

I have hardly anything running on the ipad, nothing else going on web wise, had switched from playing blitz to safari to post something here, switched back into wotb, green ping in garage, hit battle, roster comes up ... Orange circle of death! 

Game locked up, ipad locked up. 

Second time this happens since 1.7.0

Then by the time you force shut down the ipad, reboot, get on --- maybe we can skip or shorten the intros? ---

7:2 looked like somebody else just revived at spawn as I wasn't parked by myself. 

 

Previously sent to support, they want the full report, which you can't attach on the ipad, but should be sent to,them autoamtically. 

 

Whatever crashes WG thougt was fixed with 1.7, clearly aren't. 

 

Block Quote

 

{"bundleID":"net.wargaming.wotblitz","app_name":"wotblitz","share_with_app_devs":true,"name":"wotblitz","app_version":"1.7.0","is_first_party":false,"os_version":"iPhone OS 8.1.3 (12B466)","bug_type":"109","slice_uuid":"159cc93d-5301-3694-895e-563c988d2568","build_version":"1.7.0.113","adam_id":859204347}
Incident Identifier: 0C880B2B-0284-4240-9C5A-6C53F0FCF5C6
CrashReporter Key:   f4aaa4f7d6b5f6a48f2b21d9cb9cab25aae785ac
Hardware Model:      iPad3,1
Process:             wotblitz [13117]
Path:                /private/var/mobile/Containers/Bundle/Application/BC67F1C7-249E-4C42-8CF5-E8FE3E796475/WoTBlitz.app/wotblitz
Identifier:          net.wargaming.wotblitz
Version:             1.7.0.113 (1.7.0)
Code Type:           ARM (Native)
Parent Process:      launchd [1]

Date/Time:           2015-02-28 12:33:19.357 -0500
Launch Time:         2015-02-28 12:28:59.012 -0500
OS Version:          iOS 8.1.3 (12B466)
Report Version:      105

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Subtype: KERN_PROTECTION_FAILURE at 0x06e49000
Triggered by Thread:  0

Thread 0 name:  Dispatch queue: OpenGLMT
Thread 0 Crashed:
0   libsystem_kernel.dylib            0x355b8298 0x355a4000 + 82584
1   wotblitz                          0x00f93fb4 0x4000 + 16318388
2   libsystem_platform.dylib          0x356330a0 0x3562f000 + 16544
3   IMGSGX543GLDriver                 0x25da4900 0x25d98000 + 51456
4   IMGSGX543GLDriver                 0x25da4900 0x25d98000 + 51456
5   IMGSGX543GLDriver                 0x25da35b0 0x25d98000 + 46512
6   IMGSGX543GLDriver                 0x25d9d7e4 0x25d98000 + 22500
7   libGPUSupportMercury.dylib        0x2e0c5612 0x2e0c2000 + 13842
8   GLEngine                          0x29d6b026 0x29cf8000 + 471078
9   GLEngine                          0x29d0e01c 0x29cf8000 + 90140
10  GLEngine                          0x29d2085a 0x29cf8000 + 165978
11  GLEngine                          0x29d6866e 0x29cf8000 + 460398
12  libdispatch.dylib                 0x354b840c 0x354b6000 + 9228
13  libdispatch.dylib                 0x354c185c 0x354b6000 + 47196
14  GLEngine                          0x29d43d06 0x29cf8000 + 310534
15  GLEngine                          0x29d43c96 0x29cf8000 + 310422
16  wotblitz                          0x00a35050 0x4000 + 10686544
17  wotblitz                          0x00a327c8 0x4000 + 10676168
18  wotblitz                          0x009c9b98 0x4000 + 10247064
19  wotblitz                          0x00ac4a44 0x4000 + 11274820
20  wotblitz                          0x00ab9660 0x4000 + 11228768
21  wotblitz                          0x00ab884c 0x4000 + 11225164
22  wotblitz                          0x00ab8884 0x4000 + 11225220
23  wotblitz                          0x00b00830 0x4000 + 11520048
24  wotblitz                          0x00af7884 0x4000 + 11483268
25  wotblitz                          0x00962fb4 0x4000 + 9826228
26  wotblitz                          0x00965994 0x4000 + 9836948
27  wotblitz                          0x009b9260 0x4000 + 10179168
28  QuartzCore                        0x2a324ae6 0x2a2ca000 + 371430
29  QuartzCore                        0x2a32494e 0x2a2ca000 + 371022
30  IOMobileFramebuffer               0x2ebdc82c 0x2ebd7000 + 22572
31  IOKit                             0x283331ea 0x2832f000 + 16874
32  CoreFoundation                    0x273bf3a2 0x27301000 + 779170
33  CoreFoundation                    0x273cf7f0 0x27301000 + 845808
34  CoreFoundation                    0x273cf78a 0x27301000 + 845706
35  CoreFoundation                    0x273cddac 0x27301000 + 839084
36  CoreFoundation                    0x2731ab2c 0x27301000 + 105260
37  CoreFoundation                    0x2731a93e 0x27301000 + 104766
38  GraphicsServices                  0x2e6cf04c 0x2e6c6000 + 36940
39  UIKit                             0x2a90cf1c 0x2a89f000 + 450332
40  wotblitz                          0x009bb454 0x4000 + 10187860
41  libdyld.dylib                     0x354f3aac 0x354f2000 + 6828

Thread 1 name:  Dispatch queue: com.apple.libdispatch-manager
Thread 1:
0   libsystem_kernel.dylib            0x355a52c8 0x355a4000 + 4808
1   libdispatch.dylib                 0x354c7e44 0x354b6000 + 73284
2   libdispatch.dylib                 0x354c7b76 0x354b6000 + 72566

Thread 2:
0   libsystem_kernel.dylib            0x355a5568 0x355a4000 + 5480
1   wotblitz                          0x00cb3670 0x4000 + 13301360
2   wotblitz                          0x00cc9086 0x4000 + 13389958
3   libsystem_pthread.dylib           0x35637e64 0x35635000 + 11876
4   libsystem_pthread.dylib           0x35637dd6 0x35635000 + 11734
5   libsystem_pthread.dylib           0x35635b80 0x35635000 + 2944

Thread 3 name:  

 

 


 

Forum essentials:  > Desktop mode 
Check recent threads. Check WG staff threads. Use search.
    > WG Bugs and current update     > Feedback     > Vehicle Bay     > Guides     > Videos 

 

     BE  (+)   

    Got lag issues ?  >> Pingplotter thread  << 
Blitz Community Coalition | Looney Tooners | Triarii | Blitz University | Basic Training  | Mentor
 


Thomazealot #2 Posted 28 February 2015 - 06:23 PM

    Sergeant

  • Players
  • 12223 battles
  • 272
  • Member since:
    06-28-2014
I'm a bit confused on everything you are saying here, so I won't comment on the orange circle of death you speak of.  But, you can actually skip the intros, just tap the screen during them :P

sig.png


Bruder #3 Posted 28 February 2015 - 06:50 PM

    Sergeant

  • Players
  • 49875 battles
  • 281
  • [III]
  • Member since:
    06-28-2011
DUUUHHHHH...!!!!!

acrisis #4 Posted 28 February 2015 - 06:50 PM

    First Sergeant

  • Players
  • 20500 battles
  • 11,107
  • [III]
  • Member since:
    12-27-2014
Clarified my quick text a bit. Didn't know about intro skip. Must try, tx :)

 

Forum essentials:  > Desktop mode 
Check recent threads. Check WG staff threads. Use search.
    > WG Bugs and current update     > Feedback     > Vehicle Bay     > Guides     > Videos 

 

     BE  (+)   

    Got lag issues ?  >> Pingplotter thread  << 
Blitz Community Coalition | Looney Tooners | Triarii | Blitz University | Basic Training  | Mentor
 


CptCheez #5 Posted 28 February 2015 - 07:25 PM

    This Space Intentionally Left Blank

  • Players
  • 15398 battles
  • 6,798
  • Member since:
    07-08-2014
A SIGBUS exception is typically caused for one of two reasons — either the presence of a bug in the software in which it occurred, or the presence of faulty RAM.  So while it's possible that this was caused by a bug in Blitz, it's also possible that it could have been caused by a failing RAM module in your iPad.  I'd recommend taking it into the Apple Store to see if they have any diagnostic tools that can run a RAM test on your iPad.  RAM chips can and do fail, unfortunately.

"When the going gets tough and the stomach acids flow, 
The cold wind of conformity is nipping at your nose.
When some trendy new atrocity has brought you to your knees
Come with us we'll sail the Seas of Cheese."


acrisis #6 Posted 28 February 2015 - 08:40 PM

    First Sergeant

  • Players
  • 20500 battles
  • 11,107
  • [III]
  • Member since:
    12-27-2014
Thanks for chiming in cpt.
Bad ram? That wouldn't be great ...  I typically don't have any other issues or gripes, other than iOS shortcomings and Safari.  Unfortunately no Apple Store nearby, but will have to keep it in mind for when I'm near one.

 

Forum essentials:  > Desktop mode 
Check recent threads. Check WG staff threads. Use search.
    > WG Bugs and current update     > Feedback     > Vehicle Bay     > Guides     > Videos 

 

     BE  (+)   

    Got lag issues ?  >> Pingplotter thread  << 
Blitz Community Coalition | Looney Tooners | Triarii | Blitz University | Basic Training  | Mentor
 


CptCheez #7 Posted 28 February 2015 - 11:24 PM

    This Space Intentionally Left Blank

  • Players
  • 15398 battles
  • 6,798
  • Member since:
    07-08-2014

I know it's probably not what you wanted to hear, but I just wanted to let you know what the possible causes could be.  Not saying it IS bad RAM, just that it could be.  It doesn't necessarily have to be an Apple Store you take it to; any Apple Authorized Service Provider should have the tools to check it out.  Find one here:

https://locate.apple.com/lac/en/


"When the going gets tough and the stomach acids flow, 
The cold wind of conformity is nipping at your nose.
When some trendy new atrocity has brought you to your knees
Come with us we'll sail the Seas of Cheese."


CrimsonMG #8 Posted 28 February 2015 - 11:26 PM

    First Sergeant

  • Players
  • 10726 battles
  • 2,585
  • [FLOOP]
  • Member since:
    07-01-2014
I crashed twice in one battle today and logged in to see my self dead, well played 4/20.




1 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users