DOCSLIB.ORG

Crashlocator: Locating Crashing Faults Based on Crash Stacks

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Crashlocator: Locating Crashing Faults Based on Crash Stacks CrashLocator: Locating Crashing Faults Based on Crash Stacks Rongxin Wu §, Hongyu Zhang †, Shing-Chi Cheung §, and Sunghun Kim § § Department of Computer Science and Engineering The Hong Kong University of Science and Technology, Hong Kong, China {wurongxin, scc, hunkim}@cse.ust.hk † Microsoft Research Beijing 100080, China [email protected] ABSTRACT crashed modules) at the time of crash, cluster similar crash reports Software crash is common. When a crash occurs, software devel- that are likely caused by the same fault into buckets (categories), opers can receive a report upon user permission. A crash report and present the crash information to developers for debugging. typically includes a call stack at the time of crash. An important Existing crash reporting systems [2, 14, 25] mostly focus on col- step of debugging a crash is to identify faulty functions, which is lecting and bucketing crash reports effectively. Although the col- often a tedious and labor-intensive task. In this paper, we propose lected crash information is useful for debugging, these systems do CrashLocator, a method to locate faulty functions using the crash not support automatic localization of crashing faults. As a result, stack information in crash reports. It deduces possible crash traces debugging for crashes requires non-trivial manual efforts. (the failing execution traces that lead to crash) by expanding the crash stack with functions in static call graph. It then calculates Over the years, various fault localization techniques (e.g., [1, 18, the suspiciousness of each function in the approximate crash trac- 21, 22]) have been proposed to help developers locate faults. es. The functions are then ranked by their suspiciousness scores These techniques suggest a list of suspicious program entities by and are recommended to developers for further investigation. We statistically analyzing both the passing and failing execution trac- evaluate our approach using real-world Mozilla crash data. The es of test cases. Developers can then examine the ranked list to results show that our approach is effective: we can locate 50.6%, locate faults. However, these fault localization techniques assume 63.7% and 67.5% of crashing faults by examining top 1, 5 and 10 the availability of complete information of failing and passing functions recommended by CrashLocator, respectively. Our ap- execution traces, while crash reports typically contain only the proach outperforms the conventional stack-only methods signifi- crash stacks dumped at the time of crashes. cantly. In this paper, we propose CrashLocator, a novel technique for Categories and Subject Descriptors locating crashing faults based on crash stacks and static analysis techniques. Our technique is targeting at locating faulty functions D.2.5 [ Software Engineering ]: Testing and Debugging- as functions are commonly used in unit testing and helpful for Debugging Aids. crash reproducing [5, 16]. For a widely-used system, one crashing General Terms fault could trigger a large number of crash reports. Therefore, a Measurement, Reliability sufficient number of crash stacks can be used by CrashLocator for crashing fault localization. Keywords CrashLocator expands crash stacks into approximate crash traces Crashing fault localization, crash stack, software crash, statistical (the failing execution traces that lead to crash) using static analy- debugging, software analytics. sis including call graph analysis, control flow analysis, and back- ward slicing. For effective fault localization, CrashLocator applies 1. INTRODUCTION the concept of term-weighting [24]: locating crashing faults is Software crashes are severe manifestations of software faults. treated as the problem of term weighting, i.e., calculating the im- Crashes are often required to be fixed with a high priority. Recent- portance of a function (term) for a bucket of crash traces (docu- ly, many crash reporting systems such as Windows Error Report- ments). CrashLocator considers several factors to weigh a func- ing [14], Apple Crash Reporter [2], and Mozilla Crash Reporter tion: the frequency of a function appearing in a bucket of crash [25] have been proposed and deployed. These systems automati- traces, the frequency of a function appearing in crash traces of cally collect relevant information (such as the crash stack and different buckets, the distance between a function and the crash point, and the size of a function. Using these factors, CrashLoca- tor calculates the suspiciousness score of each function in the Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed approximate crash traces. Finally, it returns a ranked list of suspi- for profit or commercial advantage and that copies bear this notice and the full citation cious faulty functions to developers. The developers can examine on the first page. Copyrights for components of this work owned by others than ACM the top N returned functions to locate crashing faults. must be honored. Abstracting with credit is permitted. To copy otherwise, or republis h, to post on servers or to redistribute to lists, requires prior specific permission and/or a We evaluate CrashLocator using real crash data from three differ- fee. Request permissions from [email protected]. ent Mozilla products, Firefox, Thunderbird and SeaMonkey. The ISSTA'14, July 21 –25, 2014, San Jose, CA, USA . evaluation results are promising: using CrashLocator developers Copyright 2014 ACM 978-1-4503-2645-2/14/07... $15.00. can locate 50.6%, 63.7% and 67.5% of crashing faults by examin- Figure 2 is an example of crash stack in a Firefox crash report ing top 1, 5 and 10 functions in the returned ranked list, respec- (crash ID: f2f55573-e2cd-4ce9-92be-b16e72130904 ). The pro- tively. In addition, the evaluation results show that our approach gram crashed at Frame 0. Each frame contains a full-qualified outperforms the conventional stack-only approaches. function name and the source file position (source file name and line number). The main contributions of this paper are as follows: In large-scale systems such as Microsoft Windows and Mozilla- · We propose a novel technique for locating crashing faults. Firefox, developers receive a large number of crash reports sent Our framework is based on crash stacks only and does not by users at deployment sites. These crash reports are automatical- require additional information from deployment sites or ly grouped into different buckets, according to the crashed method program instrumentation. To our best knowledge, this is the signatures [25]. The grouping is based on the assumptions that a first time such a technique is proposed. crashing fault results in the same crashed method or similar · We implement our technique and evaluate our approach stacks. Ideally, each bucket should correspond to a unique crash- using Mozilla products, which are real and popular projects. ing fault. In this paper, our research goal is to locate the faulty function given a bucket of crash reports. The remainder of this paper is organized as follows: We introduce Frame 0 background information in Section 2. Section 3 introduces some Crash Signature nsWindow::ClearCachedResources() widget/windows/nsWindow.cpp:7821 nsWindow::ClearResourcesCallback(HWND__ *,long) observations based on our empirical study and formulates the Frame 1 crashing fault localization problem. Section 4 describes our ap- widget/windows/nsWindow.cpp:7812 proach. Section 5 presents our experimental design and Section 6 … Frame 63 mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate *) shows the experimental results. We discuss issues involved in our ipc/glue/MessagePump.cpp:117 MessageLoop::RunHandler() approach in Section 7 and threats to validity in Section 8. Section Frame 64 9 surveys related work followed by the conclusion in Section 10. ipc/chromium/src/base/message_loop.cc:201 Frame 65 xul.dll@0x16d800 2. BACKGROUND Figure 2. A crash stack example. Despite immense efforts spent on software quality assurance, released software products are often shipped with faults. Some 3. CRASH LOCALIZATION PROBLEM faults manifest as crashes after software deployment. The crash information from deployment sites is useful for debugging crash- 3.1 Challenges for Locating Crashing Faults es. A crash report typically contains limited information such as crashed method signature and crash stacks. The execution context, including structural coverage, under which the fault was triggered, is unavailable. Localization of faulty functions based on such limited information is challenging. More specifically, we have identified the following two main challenges: incomplete crash trace and uncertain fault location. Crash Reporting System Incomplete crash trace Crash Information Crash stacks only contain partial crash (failing) traces and do not Software Crash with Crash Stack contain information of complete passing execution traces. There- fore, many conventional fault localization techniques cannot be applied. These fault localization techniques allow programmers to locate faults by examining a small portion of code [1, 18, 21, 22]. They contrast the passing execution traces with the failing ones, compute fault suspiciousness of individual program elements (such as statements and predicates), and present a list of program Developers Bug Reports Crash Buckets elements ranked by their fault suspiciousness. These techniques are not directly
Load more

Recommended publications
  • Challenges and Issues of Mining Crash Reports
    Challenges and Issues of Mining Crash Reports Le An, Foutse Khomh SWAT, Polytechnique Montreal,´ Quebec,´ Canada fle.an, [email protected] Abstract—Automatic crash reporting tools built in many soft- In the rest of this paper, we describe the structure of a ware systems allow software practitioners to understand the crash report before presenting some analytic techniques to origin of field crashes and help them prioritise field crashes mine implicit information from crash reports. For each of the or bugs, locate erroneous files, and/or predict bugs and crash occurrences in subsequent versions of the software systems. In techniques, we discuss its challenges and issues. After giving this paper, after illustrating the structure of crash reports in an overview of the related work, we conclude the paper with Mozilla, we discuss some techniques for mining information from suggestions for future studies. crash reports, and highlight the challenges and issues of these techniques. Our aim is to raise the awareness of the research II. STRUCTURE OF CRASH REPORTS community about issues that may bias research results obtained In this section, we take crash reports from Mozilla Socorro from crash reports and provide some guidelines to address certain server (Mozilla’s crash collecting database) [4] as an example challenges related to mining crash reports. Index Terms—Crash report, bug report, mining software to describe the typical crash collecting system. repositories. Mozilla delivers its applications with a built-in automatic crash reporting tool: Mozilla Crash Reporter, which sends a crash report to the Mozilla Socorro server, once end users I. INTRODUCTION encounter an unexpected halt of the application.
    [Show full text]
  • Crash Reporting: Mozilla’S Open Source Solution
    Crash Reporting: Mozilla’s Open Source Solution K Lars Lohn Ted Mielczarek Austin King Friday, July 24, 2009 Howdy, I’m Lars from Mozilla, I’m here today with my colleagues, Ted Mill-char-ek and Austin King to talk about Crash Reporting. What is it? Friday, July 24, 2009 Have you ever seen Firefox crash? Have you ever wondered what happens after you hit the “restart firefox” button? In the next 45 minutes, we’re going to take you down the rabbit hole and show you what we do. We want our processes to be open. When you experience a problem with any Mozilla product, we want _everyone_, not just the developers, to watch the flow of information about a problem for its initial occurrence, through data collection and triage, on to Bugzilla and to an eventual resolution. Crash reporting is the transmission of information to the developers about the state of an application during a catastrophic failure. Friday, July 24, 2009 Crash reporting is the transmission of information about the state of an application during a catastrophic failure to the developers. The goal is to give the developers information that they would not otherwise have had. Google Socorro Socorro UI Breakpad Server (reporter) minidump_stackwalk Friday, July 24, 2009 Our crash reporting system can be divided into three parts. Breakpad - a google project - this code lives mainly within the Firefox application Socorro (in two movements) the backend server and the user interface running at Mozilla. written in three languages <click> <click> <click> Ted, Austin and I are the three developers in charge of the three sections.
    [Show full text]
  • An Autopsy of a Web Browser's Leaked Crash Reports
    Crashing Privacy: An Autopsy of a Web Browser’s Leaked Crash Reports Kiavash Satvat Nitesh Saxena University of Alabama at Birmingham University of Alabama at Birmingham [email protected] [email protected] ABSTRACT private information that can be found in crash reports which may Harm to the privacy of users through data leakage is not an un- pose a threat to the users’ privacy. known issue, however, it has not been studied in the context of In this paper, to demonstrate possible risks that the current the crash reporting system. Automatic Crash Reporting Systems implementation of ACRS may pose to users’ privacy, we study a (ACRS) are used by applications to report information about the er- dataset of partially anonymized crash reports released by one of 1 rors happening during a software failure. Although crash reports the major browsers . The current state of the art browsers collect are valuable to diagnose errors, they may contain users’ sensitive relatively similar data including browsed URL during the crash and information. In this paper, we study such a privacy leakage vis-a- runtime information, as they can be required for the debugging. vis browsers’ crash reporting systems. As a case study, we mine To the best of our knowledge, this is the first case study which a dataset consisting of crash reports collected over the period of scrutinizes a database of 2.5 million partially anonymized crash re- six years. Our analysis shows the presence of more than 20,000 ports, containing visited URLs, system runtime information and sessions and token IDs, 600 passwords, 9,000 email addresses, an users’ descriptions.
    [Show full text]
  • Why Did This Reviewed Code Crash? an Empirical Study of Mozilla Firefox
    Why Did This Reviewed Code Crash? An Empirical Study of Mozilla Firefox Le An and Foutse Khomh Shane McIntosh Marco Castelluccio Polytechnique Montréal McGill University Mozilla Corporation and Università Federico II {le.an, foutse.khomh}@polymtl.ca [email protected] [email protected] Abstract—Code review, i.e., the practice of having other team mine the crash collection, version control, issue tracking, and members critique changes to a software system, is a pillar of code reviewing systems of the Mozilla Firefox project. More modern software quality assurance approaches. Although this specifically, we address the following two research questions: activity aims at improving software quality, some high-impact defects, such as crash-related defects, can elude the inspection of RQ1: What are the characteristics of reviewed code that is reviewers and escape to the field, affecting user satisfaction and implicated in a crash? increasing maintenance overhead. In this research, we investigate We find that crash-prone reviewed patches often contain the characteristics of crash-prone code, observing that such code complex code, and classes with many other classes de- tends to have high complexity and depend on many other classes. In the code review process, developers often spend a long time on pending on them. Crash-prone patches tend to take a and have long discussions about crash-prone code. We manually longer time and generate longer discussion threads than classify a sample of reviewed crash-prone patches according to non-crash-prone patches. This result suggests that review- their purposes and root causes. We observe that most crash- ers need to focus their effort on the patches with high prone patches aim to improve performance, refactor code, add complexity and on the classes with a complex relationship functionality, or fix previous crashes.
    [Show full text]
  • City Research Online
    City Research Online City, University of London Institutional Repository Citation: Stankovic, V. and Strigini, L. (2009). A survey on online monitoring approaches of computer-based systems. London, UK: Centre for Software Reliability, City University London. This is the unspecified version of the paper. This version of the publication may differ from the final published version. Permanent repository link: https://openaccess.city.ac.uk/id/eprint/531/ Link to published version: Copyright: City Research Online aims to make research outputs of City, University of London available to a wider audience. Copyright and Moral Rights remain with the author(s) and/or copyright holders. URLs from City Research Online may be freely distributed and linked to. Reuse: Copies of full items can be used for personal research or study, educational, or not-for-profit purposes without prior permission or charge. Provided that the authors, title and full bibliographic details are credited, a hyperlink and/or URL is given for the original metadata page and the content is not changed in any way. City Research Online: http://openaccess.city.ac.uk/ [email protected] A survey on online monitoring approaches of computer-based systems Prepared by: Vladimir Stankovic, Lorenzo Strigini Date : June 2009 Version : 2.6 1/29 This report 1 surveys forms of online data collection that are in current use (as well as being the subject of research to adapt them to changing technology and demands), and can be used as inputs to assessment of dependability and resilience, although they are not primarily meant for this use. 1. Introduction Monitoring the components of a system can be used to make decisions about the management of the system and thus control its behaviour.
    [Show full text]
  • The Unreasonable Effectiveness of Traditional Information Retrieval in Crash Report Deduplication
    The Unreasonable Effectiveness of Traditional Information Retrieval in Crash Report Deduplication Joshua Charles Eddie Antonio Santos Abram Hindle Campbell Department of Computing Department of Computing Department of Computing Science Science Science University of Alberta University of Alberta University of Alberta Edmonton, Canada Edmonton, Canada Edmonton, Canada [email protected] [email protected] [email protected] ABSTRACT Organizations like Mozilla, Microsoft, and Apple are flooded Ada is a senior software engineer at Lovelace Inc., a large with thousands of automated crash reports per day. Al- software development company. Lovelace has just shipped though crash reports contain valuable information for de- the latest version of their software to hundreds of thousands bugging, there are often too many for developers to examine of users. A short while later, as Ada is transitioning her team individually. Therefore, in industry, crash reports are often to other projects, she gets a call from the quality-assurance automatically grouped together in buckets. Ubuntu’s repos- team (QA) saying that the software she just shipped has itory contains crashes from hundreds of software systems a crashing bug affecting two-thirds of all users. Worse yet, available with Ubuntu. A variety of crash report bucket- Ada and her team can’t replicate the crash. What would ing methods are evaluated using data collected by Ubuntu’s really be helpful is if every time that crash was encountered Apport automated crash reporting system. The trade-off be- by a user, Lovelace would automatically receive a crash re- tween precision and recall of numerous scalable crash dedu- port [1], with some context information about what machine plication techniques is explored.
    [Show full text]
  • Supporting Software Development Based on Crash Report Mining and Analysis
    CrashAwareDev: Supporting Software Development based on Crash Report Mining and Analysis Leandro Beserra*y, Roberta Coelhoy *Informatics Superintendence yDepartment of Informatics and Applied Mathematics Federal University of Rio Grande do Norte Natal, Brazil [email protected], [email protected] Abstract— Exception handling mechanisms are a com- of a program [2], allowing exceptions to be th- mon feature of mainstream programming languages to rown, captured, and handled at different points deal with exceptional conditions. If on the one hand in the system. However, the exception handling they allow the programmer to prepare the code to deal code designed to make a system more robust often with exceptional conditions, on the other hand they can become a source of bugs that threatens the application works the other way around and become a burden robustness – studies have shown that uncaught exceptions programmers has to cope with, leading to bugs are the main cause of application crashes. To keep track such as the uncaught exceptions. The uncaught of crashes and enable an easier fault localization, several exceptions are the main cause of crashes in Java applications, nowadays, use crash reporting tools. In software systems [3]. A crash is an abnormal this work, we propose a tool named CrashAwareDev, behavior of a system that leads to the interruption integrated with the Eclipse IDE, which mines the in- formation available in crash reporting tools to support of its execution. programmers in their day-to-day activities. The proposed After a crash occurs, systems typically store tool alerts developers about the classes related to recent information related to the crash on crash report crashes and warns about source code characteristics (bug systems.
    [Show full text]
  • Privacy-Aware Remote Error Analysis on Commodity Software
    Panalyst: Privacy-Aware Remote Error Analysis on Commodity Software Rui Wang†, XiaoFeng Wang† and Zhuowei Li‡ †Indiana University at Bloomington, ‡Center for Software Excellence, Microsoft wang63,xw7 @indiana.edu, [email protected] { } Abstract typically achieved by running an error reporting tool on a client system, which gathers data related to an applica- Remote error analysis aims at timely detection and rem- tion’s runtime exception (such as a crash) and transmits edy of software vulnerabilities through analyzing run- them to a server for diagnosis of the underlying software time errors that occur on the client. This objective can flaws. This paradigm has been widely adopted by soft- only be achieved by offering users effective protection ware manufacturers. For example, Microsoft relies on of their private information and minimizing the perfor- WER to collect data should a crash happen to an applica- mance impact of the analysis on their systems without tion. Similar tools developed by the third party are also undermining the amount of information the server can extensively used. An example is BugToaster [27], a free access for understanding errors. To this end, we propose crash analysis tool that queries a central database using in the paper a new technique for privacy-aware remote the attributes extracted from a crash to seek a potential analysis, called Panalyst. Panalyst includes a client com- fix. These tools, once complemented by automatic anal- ponent and a server component. Once a runtime excep- ysis mechanisms [44, 34] on the server side, will also tion happens to an application, Panalyst client sends the contribute to quick detection and remedy of critical se- server an initial error report that includes only public in- curity flaws that can be exploited to launch a large-scale formation regarding the error, such as the length of the cyber attack such as Worm epidemic [47, 30].
    [Show full text]
  • Statistical Debugging
    Statistical Debugging Ben Liblit, University of Wisconsin–Madison What’s This All About? ` Statistical Debugging & Cooperative Bug Isolation ` Observe deployed software in the hands of real end users ` Build statistical models of success & failure ` Guide programmers to the root causes of bugs ` Make software suck less ` Lecture plan 1. Motivation for post-deployment debugging 2. Instrumentation and feedback 3. Statistical modeling and (some) program analysis 4. Crazy hacks, cool tricks, & practical considerations Credit Where Credit is Due ` Alex Aiken ` Akash Lal ` David Andrzejewski ` Junghee Lim ` Piramanayagam ` Mayur Naik Arumuga Nainar ` Jake Rosin ` Ting Chen ` Umair Saeed ` Greg Cooksey ` Alice Zheng ` Evan Driscoll ` Xiaojin Zhu ` Jason Fletchall ` … and an anonymous ` Michael Jordan cast of thousands! ` Anne Mulhern ` Or maybe just hundreds? ` Garrett Kolpin ` I don’t really know Motivations: Software Quality in the Real World “There are no significant bugs in our released software that any significant number of users want fixed.” Bill Gates, quoted in FOCUS Magazine A Caricature of Software Development Requirements Architecture & Design Implementation Testing & Verification Maintenance A Caricature of Software Development Requirements Architecture & Design Implementation Testing & Verification Maintenance Software Releases in the Real World [Disclaimer: this may also be a caricature.] Software Releases in the Real World 1. Coders & testers in tight feedback loop ` Detailed monitoring, high repeatability ` Testing approximates
    [Show full text]
  • A Crash Reporting Library for Android
    Masaryk University Faculty of Informatics A Crash Reporting Library for Android Master’s Thesis Marek Osvald Brno, Autumn 2017 Masaryk University Faculty of Informatics A Crash Reporting Library for Android Master’s Thesis Marek Osvald Brno, Autumn 2017 This is where a copy of the official signed thesis assignment and a copy ofthe Statement of an Author is located in the printed version of the document. Declaration Hereby I declare that this paper is my original authorial work, which I have worked out on my own. All sources, references, and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Marek Osvald Advisor: prof. RNDr. Václav Matyáš M.Sc. Ph.D. i Acknowledgement This work was carried out during the years 2016-2017 at AVG Technolo- gies CZ and the Faculty of Informatics at the Masaryk University in Brno. It is a pleasure to use this page to sincerely thank all the people contributing or otherwise involved in the development of this thesis. I owe my deepest gratitude to my thesis supervisor, professor Václav Matyáš. His continuous support helped me to write a thesis worthy of a prestigious institution such as the Masaryk University. I am deeply grateful to my technical supervisor Petr Koudelka for his continuous optimism and guidance during the development. His advise helped me on countless occasions. I would like to express my most sincere gratitude to Philip M. Gammon who answered my English-related questions and selflessly offered proofreading this text. I am particularly grateful for support given by Katarína Varačková and Petr Buno during the initial prototype development.
    [Show full text]
  • Stephen a Ridley
    Escaping The Sandbox (Summer 2010) SyScan-EuSecWest-ReCon Stephen A. Ridley Senior Researcher Matasano Security [email protected] @s7ephen (Twitter) Thursday, July 15, 2010 Who I am. Stephen A. Ridley Senior Security Researcher (Matasano) • Previously: Senior Security Architect at McAfee, founding member of Security Architecture Group • Prior to that: Researcher at leading Defense contractor. Directly supported U.S. Defense and Intelligence communities in realm of software exploitation and software reverse engineering • Columnist for/interviewed by IT magazines (Wired, Ping!, Washington Post) • Kenshoto DefCon CTF organizers for a few years • blog: http://www.dontstuffbeansupyournose.com • Guest Lecturer/Instructor (New York University, Netherlands Forensics Institute, Department of Defense, Google, et al) • My Focus: software reverse engineering, software development, software exploitation, software security, Kernels (Microsoft ones for now). Increasingly interested in embedded systems and mobile devices Thursday, July 15, 2010 What am I talkin’ ‘bout today? ★ Sandboxing Overview (very brief ;-) • Goals, Sandbox Architecture (Chrome) ★ Sandboxes from a User-space Perspective • Securable Objects and SID apertures • Patches/Hooks/Interception • user32 issues ★ Sandboxes from a Kernel-space Perspective • Between User-space and Kernel-space • Kernel supported “Quasi Securable Objects”, Native API • Job Objects handle the rest, or do they? ★ Tools/Techniques/Demos • SandKit Toolkit (code injection, copymem, memdiff, hookfix, sa7shell, bincompare, dumptoken, tokenbrute, handlebrute) • Using Sandbox PoC Project (from Google) • Using kernel debugger while attacking Chrome • Triggering Chrome Bugs and where to start Thursday, July 15, 2010 Presentation Focus ★ Sandbox implementations are (by their nature) strongly coupled to the Operating System ★ This presentation focuses on Microsoft Windows Operating Systems and the NT Kernel (XP and Vista) • Side Note: Check out OSX’s DAC/Sandbox.
    [Show full text]
  • Look 360: an Android Application Using Google Analytics and Firebase with Mobile Cloud Computing
    International Journal of Scientific & Engineering Research Volume 12, Issue 3, March-2021 ISSN 2229-5518 50 Look 360: An android application using Google analytics and firebase with Mobile Cloud Computing. Rawat Deepak Umesh Prathamesh Sonawane Swapnil H Patil UG Student,PHCASC,Rasayani UG Student,PHCASC,Rasayani Asst.Professor ,PHCASC,Rasayani [email protected] [email protected] [email protected] 8355974361 8308380232 9699900007 Abstract— Look 360 is an Android Mobile Application; the name “Look360” originates by keeping its features in mind and considering its capabilities of storing Events, Seminars, Trade Shows and Conferences all across India on the Basis of different categories which has high search index as well as interest of the Students and Educators. Since, Look 360 handles the storing Events, Seminars, Trade Shows and Conferences Nationwide; filtration plays an important role here. This Android Application is connected with Google Firebase which uses Real Time Database feature. Using Real-Time Database enables the system to make changes with respect to Names of events, Date and Time and Venue of events too as specified by the Organizing Team. In order to make a Fully Dynamic Native Android Application the static contents need to be connected with the Cloud, thus Firebase Remote Config comes in picture to make Text, Colour etc feel dynamic. Look 360 is integrated with Google Action which can be evoked by just saying, “Ok Google, Talk to Look 360” where users can Operates the Application based on Voice Command. Google Action used Artificial Intelligence to get output based on Human Interactions via Keyboard or Voice. This Dynamic Android Application not only have Interesting User Interface (UI) but also it built by keeping User Experience (UX) among top priorities.
    [Show full text]